linux-ext4 - Re: Filessystem corruptions while using rsnapshot

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 09 Sep 2009 09:40:41 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	Markus Trippelsdorf <markus@...ppelsdorf.de>
CC:	linux-ext4@...r.kernel.org
Subject: Re: Filessystem corruptions while using rsnapshot

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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html