All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Howorth <dave@howorth.org.uk>
To: linux-xfs@vger.kernel.org
Subject: XFS mount problem
Date: Sat, 6 Oct 2018 14:03:17 +0100	[thread overview]
Message-ID: <20181006140317.148fe46d@acer-suse.lan> (raw)

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.

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.

# l /dev/mint_vg/live-tv_lv
lrwxrwxrwx 1 root root 7 Oct  6 09:45 /dev/mint_vg/live-tv_lv -> ../dm-3

The XFS filesystem is in an LV. lv/pv/vgscan all report everything
normal; I don't think there's a problem at the LVM level.

I tried xfs_repair -n:

# xfs_repair -n /dev/dm-3
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.


This is openSUSE 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 :)

             reply	other threads:[~2018-10-06 20:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-06 13:03 Dave Howorth [this message]
2018-10-06 14:22 ` XFS mount problem Eric Sandeen
2018-10-06 15:28   ` Dave Howorth
2018-10-06 19:59     ` Eric Sandeen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20181006140317.148fe46d@acer-suse.lan \
    --to=dave@howorth.org.uk \
    --cc=linux-xfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.