-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2018-10-06 at 12:11 +0100, Dave Howorth wrote:
We had a very brief power-glitch last night, but it was enough to cause my PC to reboot. But the reboot didn't come up cleanly.
It was complaining about not being able to mount an XFS filesystem that I use for storing recorded TV programmes. In fact mount claims 'wrong fs type':
# mount -v /srv/live-tv/ mount: /srv/live-tv: wrong fs type, bad option, bad superblock on /dev/mapper/mint_vg-live--tv_lv, missing codepage or helper program, or other error.
fstab copied from later on msg:
# grep live-tv /etc/fstab #LABEL=LiveTV /srv/live-tv xfs noatime,noacl 0 2 /dev/mint_vg/live-tv_lv /srv/live-tv xfs noatime,noacl 0 2
At this step I would have tried: mount -v /dev/mint_vg/live-tv_lv /mount Now, what is /dev/mint_vg/? lvm? Maybe it is broken and you have to repair that first - which is the reason I don't use lvm.
I tried to run xfs_check but it doesn't seem to be in the repositories so I tried xfs_repair -n:
Telcontar:~ # fsck.xfs If you wish to check the consistency of an XFS filesystem or repair a damaged filesystem, see xfs_repair(8). Telcontar:~ # which fsck.xfs /sbin/fsck.xfs Telcontar:~ # l /sbin/fsck.xfs lrwxrwxrwx 1 root root 18 Oct 4 08:37 /sbin/fsck.xfs -> /usr/sbin/fsck.xfs* Telcontar:~ # l /usr/sbin/fsck.xfs - -rwxr-xr-x 1 root root 433 Aug 28 14:10 /usr/sbin/fsck.xfs* Telcontar:~ # xfs_check is an old name. The correct ones are: Telcontar:~ # xfs[tab][tab] xfs xfs_bmap xfs_db xfs_freeze xfs_growfs xfs_io xfs_mdrestore xfs_mkfile xfs_quota xfs_rtcp xfsettingsd xfsinvutil xfs_admin xfs_copy xfs_estimate xfs_fsr xfs_info xfs_logprint xfs_metadump xfs_ncheck xfs_repair xfsdump xfsinfo xfsrestore Telcontar:~ # xfs
# xfs_repair -n /dev/dm-3
-n No modify mode. Specifies that xfs_repair should not modify the filesystem but should only scan the filesystem and indicate what repairs would have been made.
Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... sb_ifree 81, counted 80 sb_fdblocks 12504226, counted 12276402 - 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 imap claims a free inode 135 is in use, would correct imap and clear inode - 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 = 1 entry "Coronation Street Omnibus.ts" at block 0 offset 3848 in directory inode 96 references free inode 135 would clear inode number in entry at offset 3848... - agno = 3 - agno = 2 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... entry "Coronation Street Omnibus.ts" in directory inode 96 points to free inode 135, would junk entry bad hash table for directory inode 96 (no data entry): would rebuild - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.
Nothing written. Good.
The mount is being tried against fstab:
# grep live-tv /etc/fstab #LABEL=LiveTV /srv/live-tv xfs noatime,noacl 0 2 /dev/mint_vg/live-tv_lv /srv/live-tv xfs noatime,noacl 0 2
I normally mount this filesystem by label but I commented that out to get the system to boot and I added the /dev line as a more basic method to see if it helped, but it gives the same error.
lv/pv/vgscan all report everything normal.
This is Leap 15.0
I'm a bit stuck now; my XFS foo is not strong today, it seems. Can anybody suggest what my next steps should be? I'll keep googling but I hope somebody may have more informed ideas :)
I suspect that lg first, but I'm not an expert. Then I'd ask on the XFS mail list. - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlu4ot4ACgkQtTMYHG2NR9UhuQCgkhrbLArV6y0CN2BhgwVRB68A WOUAoJZ4Yck4Mvq8oD8NQmOnSnwrNRb1 =C6vK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org