Bug 27003

mga7, x86_64

Updated the four packages.

A list of the utilities included in zfsprogs can be viewed at 
http://www.linuxfromscratch.org/blfs/view/svn/postlfs/xfsprogs.html

21 programs are listed, all /sbin commands.
We have 23 commands:
# ls *xfs*
fsck.xfs*   xfs_db*        xfs_info*       xfs_mkfile*  xfs_scrub*
mkfs.xfs*   xfs_estimate*  xfs_io*         xfs_ncheck*  xfs_scrub_all*
xfs_admin*  xfs_freeze*    xfs_logprint*   xfs_quota*   xfs_spaceman*
xfs_bmap*   xfs_fsr*       xfs_mdrestore*  xfs_repair*
xfs_copy*   xfs_growfs*    xfs_metadump*   xfs_rtcp*

The scrub commands are additional.

Ran diskdrake under strace and created an XFS filesystem on a tiny spare partition /dev/sda2 (780MB).  Mounted it on /mnt/xfs1 from diskdrake then copied a random file onto it.
# ls -l /dev/sda2
brw-rw---- 1 root disk 8, 2 Jul 28 16:43 /dev/sda2
# cat /etc/fstab | grep xfs
UUID=7858a545-a894-4835-8f07-a76b53e7dc88 /mnt/xfs1 xfs noatime,user_xattr 1 2

$ grep xfs trace.xfs
$
So, looks like diskdrake does not use make.xfs or the xfs library.

Check without effecting any repairs.
# xfs_repair -n /dev/sda2
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 2
        - agno = 3
        - agno = 1
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.

# xfs_metadump /dev/sda2 dumpfile
# cat dumpfile
<binary data>
# file dumpfile
dumpfile: XFS filesystem metadump image

xfs_scrub seems to be another repair program which descends as far as file level if required.  Avoided running it:
EXPERIMENTAL xfs_scrub program in use! Use at your own risk!

# xfs_admin -l -u /dev/sda2 
label = ""
UUID = 7858a545-a894-4835-8f07-a76b53e7dc88

# xfs_bmap -l -n 10 /mnt/xfs1
foreign file active, bmap command is for XFS filesystems only
<The argument should be a "file" according to usage>
xfs_bmap [ -adelpv ] [ -n num_extents ] file

Testing this requires a little more knowledge so should we pass this on the basis of a clean install?

CC: (none) => tarazed25

$ urpmq --whatrequires lib64xfs1
lib64xfs-devel
lib64xfs1
nfs-ganesha-xfs
xfsdump

Tried playing with xfsdump but none of the command options worked.

MGA7-64 Plasma on Lenovo B50
No installation issues.
Ref bug 26694 for tests.
Using a 16Gb USB stick.
]# mkfs.xfs  -f /dev/sdb
meta-data=/dev/sdb               isize=512    agcount=4, agsize=976832 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=1
data     =                       bsize=4096   blocks=3907328, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

That made the stick only accessible to root, so opened it to the world. Created as normal user a text file, inserted the stick in my desktop PC, there  could read the file.

Back at the laptop with the stick
# mount | grep sdb
/dev/sdb on /run/media/tester7/519dc13a-472d-42a3-8b70-2b66a427e58a type xfs (rw,nosuid,nodev,relatime,attr2,inode64,logbufs=8,logbsize=32k,noquota,uhelper=udisks2)

#  xfs_bmap /run/media/tester7/519dc13a-472d-42a3-8b70-2b66a427e58a
/run/media/tester7/519dc13a-472d-42a3-8b70-2b66a427e58a: no extents

#  xfs_info /run/media/tester7/519dc13a-472d-42a3-8b70-2b66a427e58a
meta-data=/dev/sdb               isize=512    agcount=4, agsize=976832 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=1, sparse=1, rmapbt=0
         =                       reflink=1
data     =                       bsize=4096   blocks=3907328, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0, ftype=1
log      =internal log           bsize=4096   blocks=2560, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

#  xfs_estimate /run/media/tester7/519dc13a-472d-42a3-8b70-2b66a427e58a
/run/media/tester7/519dc13a-472d-42a3-8b70-2b66a427e58a will take about 4.4 megabytes

Which is all similar to the refered bug, so OK

P.S.: Len, you're not lazy enough to profit from previous bugs ;-)

Whiteboard: (none) => MGA7-64-OK
CC: (none) => herman.viaene

Real hardware - AMD Athlon x3, Nvidia 390 driver

The following 3 packages are going to be installed:

- x11-server-common-1.20.8-1.1.mga7.x86_64
- x11-server-xorg-1.20.8-1.1.mga7.x86_64
- x11-server-xwayland-1.20.8-1.1.mga7.x86_64

worked as expected after reboot.

CC: (none) => brtians1

(In reply to Brian Rockwell from comment #4)
> Real hardware - AMD Athlon x3, Nvidia 390 driver
> 
> The following 3 packages are going to be installed:
> 
> - x11-server-common-1.20.8-1.1.mga7.x86_64
> - x11-server-xorg-1.20.8-1.1.mga7.x86_64
> - x11-server-xwayland-1.20.8-1.1.mga7.x86_64
> 
> worked as expected after reboot.

fyi - Mate desktop

Wrong bug Brian.  This one is for XFS filesystem tools.

yeah - couldn't delete it.

Validating. Advisory in Comment 0.

Keywords: (none) => validated_update
CC: (none) => andrewsfarm, sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0167.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED