From: Dave Chinner <david@fromorbit.com>
To: Roger Willcocks <roger@filmlight.ltd.uk>
Cc: Brian Foster <bfoster@redhat.com>,
Kris Rusocki <kszysiu@braxis.org>,
Eric Sandeen <sandeen@sandeen.net>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>,
"Rhorer, Leslie" <Leslie.Rhorer@level3.com>,
Leslie Rhorer <lrhorer@mygrande.net>
Subject: Re: XFS File system in trouble
Date: Sun, 16 Aug 2015 08:48:40 +1000 [thread overview]
Message-ID: <20150815224840.GX3902@dastard> (raw)
In-Reply-To: <03EB8070-A6DA-4E55-ACF9-6E0153E84DA0@filmlight.ltd.uk>
On Sat, Aug 15, 2015 at 07:57:04PM +0100, Roger Willcocks wrote:
>
> On 15 Aug 2015, at 19:48, Eric Sandeen <sandeen@sandeen.net> wrote:
>
> > On 8/15/15 7:28 AM, Roger Willcocks wrote:
> >> xfs_repair 3.2.1 runs cleanly.
> >>
> >> xfs_repair 3.1.1 complains about a load of stuff, including:
> >
> > I wouldn't expect v3.1.1 to work at all, because:
> >
> > # db/xfs_db -V
> > xfs_db version 4.2.0-rc1
> > # db/xfs_db /mnt/test2/leslie/md0.img -c version
> > versionnum [0xbdb4+0x8a] = V4,NLINK,DIRV2,ATTR,ALIGN,DALIGN,LOGV2,EXTFLG,SECTOR,MOREBITS,ATTR2,LAZYSBCOUNT,PROJID32BIT
> >
> > the filesystem has 32-bit project IDs, and:
> >
> > # git log --oneline | grep -i "projid32bit"
> > dd536e1 xfsprogs: Note projid32bit default change in mkfs.xfs manpage
> > 22bc10e xfsprogs: projid32bit handling
> >
> > # git describe --contains 22bc10e
> > v3.1.4~2
> >
> > that feature support didn't show up until v3.1.4. Were you running a stock v3.1.1?
> >
> > Anyway, in my testing, up to v3.2.0, repair finds a lot of errors (and spends some
> > time looking for a proper superblock)
> >
> > v3.2.1 finds no errors.
> >
>
> And there’s the problem, (since XFS_SB_VERSION2_CRCBIT is not set)
> xfs-repair-3.2.1 should spot and fix the v3 inode.
>
> repair/dinode.c (tip) only checks for (line 2335 or so):
>
> (xfs_sb_version_hascrc(&mp->m_sb) && dino->di_version < 3)
>
> not a non-crc filesystem with version >= 3.
>
> Adding the missing check:
>
> || (! xfs_sb_version_hascrc(&mp->m_sb) && dino->di_version >= 3)
Yup, that looks like the issue. Good spotting, Roger! Can you send a
patch w/ signoff that I can commit?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-08-15 22:49 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 1:46 XFS File system in trouble Rhorer, Leslie
2015-07-18 14:16 ` Eric Sandeen
2015-07-18 17:23 ` Rhorer, Leslie
2015-07-18 17:47 ` Kris Rusocki
2015-07-18 18:12 ` Leslie Rhorer
2015-07-19 1:02 ` Leslie Rhorer
2015-07-19 23:27 ` Dave Chinner
2015-07-20 7:41 ` Leslie Rhorer
2015-07-20 8:05 ` Martin Papik
2015-07-20 8:35 ` Leslie Rhorer
2015-07-20 8:52 ` Martin Papik
2015-07-20 13:08 ` Gim Leong Chin
2015-07-20 13:34 ` Eric Sandeen
2015-07-23 3:18 ` Eric Sandeen
2015-07-24 13:47 ` Leslie Rhorer
2015-07-24 14:44 ` Eric Sandeen
2015-07-24 15:29 ` Rhorer, Leslie
2015-07-20 11:17 ` Brian Foster
2015-07-23 1:45 ` Leslie Rhorer
2015-07-23 11:36 ` Brian Foster
2015-07-28 7:46 ` Leslie Rhorer
2015-07-28 8:35 ` Stefan Ring
2015-07-28 10:48 ` Roger Willcocks
2015-07-28 12:33 ` Brian Foster
2015-07-28 15:13 ` Leslie Rhorer
2015-07-28 16:53 ` Eric Sandeen
2015-07-28 19:12 ` Martin Papik
2015-07-28 19:52 ` Martin Steigerwald
2015-07-28 22:11 ` Brian Foster
2015-08-02 20:24 ` Leslie Rhorer
2015-08-04 7:52 ` Leslie Rhorer
2015-08-04 12:19 ` Brian Foster
2015-08-04 22:42 ` Dave Chinner
2015-08-10 1:37 ` Leslie Rhorer
2015-08-13 6:21 ` Leslie Rhorer
2015-08-14 1:26 ` Dave Chinner
2015-08-14 23:12 ` Leslie Rhorer
2015-08-15 12:28 ` Roger Willcocks
2015-08-15 18:48 ` Eric Sandeen
2015-08-15 18:57 ` Roger Willcocks
2015-08-15 22:48 ` Dave Chinner [this message]
2015-08-15 19:00 ` Eric Sandeen
2015-08-15 19:13 ` Roger Willcocks
2015-08-16 0:32 ` Eric Sandeen
2015-08-18 2:14 ` Dave Chinner
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=20150815224840.GX3902@dastard \
--to=david@fromorbit.com \
--cc=Leslie.Rhorer@level3.com \
--cc=bfoster@redhat.com \
--cc=kszysiu@braxis.org \
--cc=lrhorer@mygrande.net \
--cc=roger@filmlight.ltd.uk \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.com \
/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.