On Wed, Sep 09, 2009 at 09:40:41AM -0500, Eric Sandeen wrote: > 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? Eric, I'm sorry that I may have wasted your time with this. It turned out that a bad RAM module was the most likely cause of these corruptions. (I've found out only today, after I got btrfs csum errors in my log, see: http://thread.gmane.org/gmane.comp.file-systems.btrfs/3613) So please accept my apologies. Thanks. -- Markus -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
