From: "Stephen Elliott" <techweb@ntlworld.com>
To: "'Theodore Ts'o'" <tytso@mit.edu>
Cc: "'Andreas Dilger'" <adilger@dilger.ca>, <linux-ext4@vger.kernel.org>
Subject: RE: 2nd Attempt - FSCK Errors
Date: Sun, 5 May 2013 12:19:30 +0100 [thread overview]
Message-ID: <002001ce4982$6a392870$3eab7950$@ntlworld.com> (raw)
In-Reply-To: <20130503213132.GA6032@thunk.org>
Understood... When I can get a debugfs dump from the device (following
advice from Netgear) I will post but this may be in 2 or 3 weeks time.
-----Original Message-----
From: Theodore Ts'o [mailto:tytso@mit.edu]
Sent: 03 May 2013 22:32
To: Stephen Elliott
Cc: 'Andreas Dilger'; linux-ext4@vger.kernel.org
Subject: Re: 2nd Attempt - FSCK Errors
On Fri, May 03, 2013 at 07:42:55PM +0100, Stephen Elliott wrote:
> One thing maybe you could explain (and Andreas gave me his take too)
> is how you can multiply assigned blocks shared with "0" files. Andreas
> offered the suggestion that they may be in the same file. If this were
> really the case, I would suspect there to be some file corruption issues
etc...
It could be that the blocks appear multiple times in the file; or it could
be the storage system is returning different data on subsequent reads from
the device.
What we need is a debugfs dump of the inode on the file system that is
having trouble. A debugfs dump of the inode from a completely underlated
file system is not useful....
- Ted
next prev parent reply other threads:[~2013-05-05 11:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 14:00 2nd Attempt - FSCK Errors Stephen Elliott
2013-04-30 16:14 ` Andreas Dilger
2013-04-30 16:25 ` Stephen Elliott
2013-04-30 17:58 ` Stephen Elliott
2013-05-03 10:55 ` Stephen Elliott
2013-05-03 13:14 ` Theodore Ts'o
2013-05-03 13:31 ` Stephen Elliott
2013-05-03 15:29 ` Theodore Ts'o
2013-05-03 18:42 ` Stephen Elliott
2013-05-03 21:31 ` Theodore Ts'o
2013-05-05 11:19 ` Stephen Elliott [this message]
2013-05-08 14:45 ` Stephen Elliott
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='002001ce4982$6a392870$3eab7950$@ntlworld.com' \
--to=techweb@ntlworld.com \
--cc=adilger@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--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).