From: Eric Sandeen <sandeen@sandeen.net>
To: C Linus Hicks <linush@verizon.net>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_repair doesn't fix sb versionnum missing attr
Date: Fri, 12 Feb 2010 15:29:37 -0600 [thread overview]
Message-ID: <4B75C841.3010105@sandeen.net> (raw)
In-Reply-To: <1266007649.7755.12.camel@lh10.linush.net>
C Linus Hicks wrote:
> On Fri, 2010-02-12 at 14:29 -0600, Eric Sandeen wrote:
>> C Linus Hicks wrote:
>>> I run:
>>>
>>> xfs_check /dev/sdc10
>>>
>>> And it reports:
>>>
>>> sb versionnum missing attr bit 10
>>>
>>> Then I run:
>>>
>>> xfs_repair /dev/sdc10
>>>
>>> And it reports output from 7 phases and "done".
>>>
>>> Again I run:
>>>
>>> xfs_check /dev/sdc10
>>>
>>> And it reports:
>>>
>>> sb versionnum missing attr bit 10
>>>
>>> Is this how it's supposed to work?
>>> Thanks for any help.
>>> Linus
>>>
>> I've never seen that before.
>>
>> This might be interesting to see:
>>
>> # xfs_db /dev/sdc10
>> xfs_db> sb 0
>> xfs_db> version
>>
>> If you want to send me a zipped-up, obfuscated metadump of the filesystem
>> I could take a quick look.
>>
>> -Eric
>
> The output from the "version" command:
>
> versionnum [0x3084+0x0] = V4,ALIGN,DIRV2,EXTFLG
>
> I'll email the metadump directly to you so as not to pollute the list.
Ok so a little less mystery here; I was concerned about how we got here,
but Linus had to manually reconstruct his superblock, hence the missing
flags.
Looks like there are selinux attributes on all the files, so of course
the sb should have the attr flags set.
This does look like one test that check has and repair doesn't.
<checking upstream for sure>
yep!
Linus, FWIW simply creating a new file on the fs with xattrs (any
old file works if selinux is on) will set the flags as if it were
the first file created w/ an attr...
[root@host Linus-repair-bug]# xfs_check sdc10-md.log.img
sb versionnum missing attr bit 10
[root@host Linus-repair-bug]# mount -o loop sdc10-md.log.img mnt/
[root@host Linus-repair-bug]# echo foobar > mnt/blah
[root@host Linus-repair-bug]# ls -Z mnt/blah
-rw-r--r-- root root root:object_r:file_t mnt/blah
[root@host Linus-repair-bug]# umount mnt
[root@host Linus-repair-bug]# xfs_check sdc10-md.log.img
[root@host Linus-repair-bug]#
I suppose that check should get added to repair though.
Care to file a bug so it doesn't get lost?
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-02-12 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 17:44 xfs_repair doesn't fix sb versionnum missing attr C Linus Hicks
2010-02-12 20:29 ` Eric Sandeen
2010-02-12 20:47 ` C Linus Hicks
2010-02-12 21:29 ` Eric Sandeen [this message]
2010-02-12 21:51 ` C Linus Hicks
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=4B75C841.3010105@sandeen.net \
--to=sandeen@sandeen.net \
--cc=linush@verizon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox