From: Rudolf Zran Subject: Re: Restoring filenames from partly damaged ext4-filesystem Date: Fri, 10 Feb 2012 17:07:53 +0000 (GMT) Message-ID: <1328893673.79058.YahooMailNeo@web132401.mail.ird.yahoo.com> References: <1328804993.34330.YahooMailNeo@web132403.mail.ird.yahoo.com> <1328822543.65833.YahooMailNeo@web132404.mail.ird.yahoo.com> <4F351E7A.2070005@fastmail.fm> Reply-To: Rudolf Zran Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: "linux-ext4@vger.kernel.org" , "debian-user@lists.debian.org" To: Bernd Schubert Return-path: In-Reply-To: <4F351E7A.2070005@fastmail.fm> Resent-Message-ID: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Id: linux-ext4.vger.kernel.org Hello Bernd!=0A=0A=0A> I have written some tools in the past to recover the= file structure of =0A> an over-formated ext3/ext4 device based on director= y blocks.=0A> With some tweaks it should be able to assign the file#inode_n= umbers in =0A> lost+found to a directory structure.=0A> Problem is that I'm= rather busy with too many other projects already. Do =0A> you know C and c= ould you add some code on your own for the lost+found =0A> assignment? I ca= n assist you, but it is unlikely that I find much time =0A> do it myself...= =0A=0AI'm not that fluent in C, but I could just give it a try. Since it's = my=0Aown data and this recovery for personal "fun" I can't do something bad= =0Awith it :) So, if you could share the code I'd be happy!=0A=0AThanks, Ru= dolf.=0A