All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Filessystem corruptions while using rsnapshot
Date: Wed, 09 Sep 2009 16:35:45 -0500	[thread overview]
Message-ID: <4AA81FB1.7000000@redhat.com> (raw)
In-Reply-To: <20090909212925.GA2011@phenom2.trippelsdorf.de>

Markus Trippelsdorf wrote:
> On Wed, Sep 09, 2009 at 12:21:21PM -0500, Eric Sandeen wrote:
>> Markus Trippelsdorf wrote:
>>> On Wed, Sep 09, 2009 at 09:40:41AM -0500, Eric Sandeen wrote:
>>>> Markus Trippelsdorf wrote:
>> ...
>>
>>>>> The bug is very simple to reproduce here. Just run rsnapshot several
>>>>> times per day and you will eventually hit the problem.
>>>> Could you provide a bzip2'd e2image -r of a corrupted filesystem for 
>>>> analysis?
>>> OK I've uploaded the file (~80 MB):
>>> http://www.2shared.com/file/7681344/d19d7154/disc_e2image.html
>>>
>>> Hope it helps.
>> Thanks, can't guarantee that the post-mortem will lead to the anwer but 
>> it's worth a look.
> 
> I also took a look myself and it turned out that my maildir, which
> contains the LKML messages of the last three months, is the root of the
> problem. I can now reproduce the bug, by simply running (e.g.):
> 
> cp -al /var/backup/hourly.3/localhost/home/markus/.maildir/lkml/. /var/tmp/debug
> 
> where /var is mounted as: "/dev/sda1 on /var type ext4 (rw,noatime,commit=60)"
> and /var/backup/hourly.3/localhost/ is a previous backup produced by rsnapshot.

 From the original post it wasn't quite clear; do you hit runtime 
corruption, indicated by the kernel logs when the fs is mounted, and a 
subsequent fsck also finds errors?

Just for completeness, if there are errors in the system logs, can you 
post them here as well?

Thanks,
-Eric

  reply	other threads:[~2009-09-09 21:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 13:30 Filessystem corruptions while using rsnapshot Markus Trippelsdorf
2009-09-09 14:40 ` Eric Sandeen
2009-09-09 14:54   ` Markus Trippelsdorf
2009-09-09 17:20   ` Markus Trippelsdorf
2009-09-09 17:21     ` Eric Sandeen
2009-09-09 21:29       ` Markus Trippelsdorf
2009-09-09 21:35         ` Eric Sandeen [this message]
2009-09-09 21:42           ` Markus Trippelsdorf
2009-09-09 21:46             ` Eric Sandeen
2009-09-09 21:50               ` Markus Trippelsdorf
     [not found]                 ` <4AA82C62.40305@redhat.com>
2009-09-10  1:11                   ` Markus Trippelsdorf
2009-09-17 20:33   ` Markus Trippelsdorf
2009-09-17 20:39     ` Eric Sandeen

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=4AA81FB1.7000000@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    /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.