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 09:40:41 -0500 [thread overview]
Message-ID: <4AA7BE69.7070406@redhat.com> (raw)
In-Reply-To: <20090909133026.GA1965@phenom2.trippelsdorf.de>
Markus Trippelsdorf wrote:
> I'm using rsnapshot (http://rsnapshot.org/) to automatically backup my
> root filesystem (btrfs) to a second harddrive running ext4. Rsnapshot
> uses rsync and a massive amount of hard links to keep multiple backups
> instantly available.
> It seems that the sheer number of hard links overwhelms ext4 and results
> in problems that require manual fsck.ext4 runs to bring the fs back to
> normal.
>
> For example this is output from fsck.ext4:
>
> Problem in HTREE directory inode <some number>
> ... node <increasing number> has invalid depth (2)
> ... node <increasing number> has bad mxhash
> ... node <increasing number> not referenced
>
> This output is repeated ad nauseam while <increasing number> increases
> at each round.
>
> 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?
Thanks,
-Eric
next prev parent reply other threads:[~2009-09-09 14:41 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 [this message]
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
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=4AA7BE69.7070406@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.