From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.codeaurora.org ([198.145.29.96]) by bombadil.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1Z2fWU-0002dc-H1 for linux-mtd@lists.infradead.org; Wed, 10 Jun 2015 12:54:27 +0000 Message-ID: <55783369.2020109@codeaurora.org> Date: Wed, 10 Jun 2015 15:54:01 +0300 From: "Brokhman, Tanya" MIME-Version: 1.0 To: Richard Weinberger , Smitha Rathnam Subject: Re: Trouble with UBIFS References: <557825BA.6030104@codeaurora.org> <557830D4.3000301@nod.at> In-Reply-To: <557830D4.3000301@nod.at> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: "linux-mtd@lists.infradead.org" List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 6/10/2015 3:43 PM, Richard Weinberger wrote: > Tanya, > > Am 10.06.2015 um 13:55 schrieb Brokhman, Tanya: >>> Retrieving data from the filesystem is not easy, it depends how much UBIFS >>> is corrupted. >>> What I do in such cases is dumping all nodes and running them thought a >>> semi-automated script which can deal with UBIFS. >> Could you please share the script? I'm facing same issues at the moment (debugging ubifs corruption). I have a binary dump of the partition. Looking for the most user-friendly tool >> to look at it. > I'll share it as soon it is a) kind of user friendly and b) all legal stuff has been sorted out. > My plan is turning it into something like a fsck.ubfs with a "fuzzy dump" mode. great. thank you! -Tanya > > Thanks, > //richard