From: Andreas Dilger <adilger@sun.com>
To: Jeremy Sanders <jss@ast.cam.ac.uk>
Cc: Eric Sandeen <sandeen@redhat.com>, Theodore Tso <tytso@mit.edu>,
linux-ext4@vger.kernel.org
Subject: Re: fsck.ext4: Group descriptors look bad... trying backup blocks...
Date: Mon, 20 Apr 2009 14:45:34 -0600 [thread overview]
Message-ID: <20090420204534.GF3209@webber.adilger.int> (raw)
In-Reply-To: <alpine.LFD.2.00.0904201953260.30497@xpc17.ast.cam.ac.uk>
On Apr 20, 2009 19:55 +0100, Jeremy Sanders wrote:
> On Mon, 20 Apr 2009, Andreas Dilger wrote:
>> On Apr 20, 2009 16:53 +0100, Jeremy Sanders wrote:
>>> On Mon, 20 Apr 2009, Eric Sandeen wrote:
>>>> One other question - do you make use of xattrs on this filesystem?
>>>
>>> No.
>>
>> If you use anything like SELinux or ACLs you would also (indirectly) be
>> using xattrs.
>
> SELinux is switched off and we haven't (knowingly) been using xattrs, but
> I remember rsync might copy copy xattrs, so perhaps they get written in
> some way...
You can check this with:
debugfs -c -R "stat {path to file inside filesystem}" /dev/XXX
and check if the "File ACL" field is non-zero:
debugfs -c -R "stat etc/hosts" /dev/sda2
debugfs 1.40.11.sun1 (17-June-2008)
/dev/sda2: catastrophic mode - not reading inode or group bitmaps
Inode: 259128 Type: regular Mode: 0644 Flags: 0x0 Generation:
2075236634
User: 0 Group: 0 Size: 2258
File ACL: 0 Directory ACL: 0
^^^^^^^^^^^ ##### this would be non-zero #####
Links: 2 Blockcount: 8
Fragment: Address: 0 Number: 0 Size: 0
ctime: 0x49812ef4 -- Wed Jan 28 21:22:12 2009
atime: 0x49ebdce3 -- Sun Apr 19 20:24:35 2009
mtime: 0x49812ef4 -- Wed Jan 28 21:22:12 2009
Size of extra inode fields: 4
Inode version: 0
BLOCKS:
(0):534546
TOTAL: 1
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2009-04-20 20:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 11:03 fsck.ext4: Group descriptors look bad... trying backup blocks Jeremy Sanders
2009-04-17 11:26 ` Jeremy Sanders
2009-04-17 11:56 ` Theodore Tso
2009-04-17 12:16 ` Jeremy Sanders
2009-04-17 17:10 ` Eric Sandeen
2009-04-17 18:51 ` Jeremy Sanders
2009-04-17 12:24 ` Jeremy Sanders
2009-04-17 16:36 ` Theodore Tso
2009-04-17 17:00 ` Eric Sandeen
2009-04-20 9:33 ` Jeremy Sanders
2009-04-20 11:35 ` Theodore Tso
2009-04-20 11:43 ` Jeremy Sanders
2009-04-20 12:48 ` Theodore Tso
2009-04-20 12:54 ` Jeremy Sanders
2009-04-20 14:49 ` Eric Sandeen
2009-04-20 15:51 ` Eric Sandeen
2009-04-20 15:53 ` Jeremy Sanders
2009-04-20 16:26 ` Eric Sandeen
2009-04-20 16:40 ` Jeremy Sanders
2009-04-20 18:28 ` Andreas Dilger
2009-04-20 18:55 ` Jeremy Sanders
2009-04-20 20:45 ` Andreas Dilger [this message]
2009-04-22 9:34 ` Jeremy Sanders
2009-04-22 9:07 ` Jeremy Sanders
2009-04-22 9:59 ` Thierry Vignaud
2009-04-24 8:27 ` Jeremy Sanders
2009-04-21 15:14 ` Thierry Vignaud
2009-04-21 15:52 ` Eric Sandeen
[not found] ` <m23ac255pp.fsf@vador.mandriva.com>
2009-04-21 16:40 ` Eric Sandeen
2009-04-21 16:56 ` Thierry Vignaud
2009-04-21 16:43 ` Theodore Tso
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=20090420204534.GF3209@webber.adilger.int \
--to=adilger@sun.com \
--cc=jss@ast.cam.ac.uk \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).