linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Jeremy Sanders <jss@ast.cam.ac.uk>
Cc: linux-ext4@vger.kernel.org
Subject: Re: fsck.ext4: Group descriptors look bad... trying backup blocks...
Date: Mon, 20 Apr 2009 08:48:10 -0400	[thread overview]
Message-ID: <20090420124810.GT19186@mit.edu> (raw)
In-Reply-To: <alpine.LFD.2.00.0904201237500.17316@xpc17.ast.cam.ac.uk>

On Mon, Apr 20, 2009 at 12:43:37PM +0100, Jeremy Sanders wrote:
> It takes a day or two to do the sync. I've only done it twice (one with  
> the old kernel, once with the new fedora testing kernel) and it happened  
> both times. I'm afraid the statistics are rather low number here.
>
> I did a different faster test (just copying my home directory lots of  
> times), but I wasn't able to get it to fail. That test didn't use much  
> disk space, however. Maybe it's worth just dd'ing a few TB of data onto  
> the device and seeing whether that fails.
>
> I didn't reboot this time - I did last time. I just unmounted the file  
> system and fsckd it. The filesystem is 8.2TB and the data is around 
> 2.5TB.

That's that's useful data.  I wish we could make it fail more quickly
on a smaller rsync, but the fact that you didn't need to reboot is
definitely useful information.

And this is a fresh rsync so no files were being deleted, rsync should
have just been writing new files to .filename.XXXXX and then renaming
the filename to filename.XXXXX when it is done, right? 

OK, let me think about this a little.  I think we can create a patch
which checks for writes to the block group descriptors and dumps a
stack trace.  That would allow us catch the failing code in question
in the act, and maybe figure out what is going on.

					- Ted

  reply	other threads:[~2009-04-20 12:48 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 [this message]
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
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=20090420124810.GT19186@mit.edu \
    --to=tytso@mit.edu \
    --cc=jss@ast.cam.ac.uk \
    --cc=linux-ext4@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 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).