From: Markus Trippelsdorf Subject: Re: Filessystem corruptions while using rsnapshot Date: Wed, 9 Sep 2009 19:20:15 +0200 Message-ID: <20090909172015.GA1980@phenom2.trippelsdorf.de> References: <20090909133026.GA1965@phenom2.trippelsdorf.de> <4AA7BE69.7070406@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-ext4@vger.kernel.org To: Eric Sandeen Return-path: Received: from smtp-out-144.synserver.de ([212.40.180.144]:1055 "HELO smtp-out-144.synserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1752994AbZIIRUO (ORCPT ); Wed, 9 Sep 2009 13:20:14 -0400 Content-Disposition: inline In-Reply-To: <4AA7BE69.7070406@redhat.com> Sender: linux-ext4-owner@vger.kernel.org List-ID: 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 > > ... node has invalid depth (2) > > ... node has bad mxhash > > ... node not referenced > > > > This output is repeated ad nauseam while 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? OK I've uploaded the file (~80 MB): http://www.2shared.com/file/7681344/d19d7154/disc_e2image.html Hope it helps. -- Markus