xfs
[Top] [All Lists]

Re: Files with non-ASCII names inaccessible after xfs_repair

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: Files with non-ASCII names inaccessible after xfs_repair
From: Zachary Kotlarek <zach@xxxxxxxxxxxx>
Date: Wed, 15 Jan 2014 00:21:35 -0800
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=kotlarek.com; s=default; t=1389774101; bh=LiI748sIHhaqHmF3bEkpPwrGs1Cm99JMQQpQRDwE5co=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Message-Id:References:To; b=M2EGdTazIzZeZmhlSYCxNrfyAMdmG15+s7lykstCTOmd4EQNrLBcdq4vH8aeQ0yyB whKhLdruLbBCzaVbpCFwQ1O8Rg6Wiv+ImgY3LEuxPrcrpIEphGNcdaPL28kJxJBJpb JVGTIUxxJ2ZgRO9MDJZodcyfaUpaAqS02owRxhjg=
In-reply-to: <20140115063722.GW3469@dastard>
References: <20140113031947.GG3469@dastard> <E2EE0AEA-ED22-4D3B-8550-88F2ED1F8314@xxxxxxxxxxxx> <20140113192732.GI3469@dastard> <0E45339E-04C4-4775-B6B0-FC55245B0AED@xxxxxxxxxxxx> <20140114022414.GM3469@dastard> <BE0C947E-37DE-4CA1-B120-59B95E1E8EB8@xxxxxxxxxxxx> <20140115015350.GR3469@dastard> <61E74CEF-8244-4E90-BA7D-91D54DADC3C1@xxxxxxxxxxxx> <20140115034803.GT3469@dastard> <1E5E569C-2E11-42A1-A771-89D4800BC412@xxxxxxxxxxxx> <20140115063722.GW3469@dastard>
On Jan 14, 2014, at 10:37 PM, Dave Chinner <david@xxxxxxxxxxxxx> wrote:

> Sure. Can you write a patch to add explanation that explain the
> problem you've had?


Will do.


>> Theoretically I could find the expected hashvals and overwrite
>> them with xfs_db, right?
> 
> In theory, but hashvals need to be ordered correctly and that
> potentially means having to update btree node pointers and all sorts
> of other complexities. xfs_db is really not designed to rewrite
> directory structures manually.


It occurs to me the other way around is probably easier anyway — change the 
name entry to something ASCII-only (of the same byte length) and let xfs_repair 
rebuild the hash. That’s what got me into this mess, so by cartoon logic it 
should fix things if I do it again. ;-)

After testing that theory on a metadata dump I spun up an LVM snapshot, where 
it also seems to work. So that gets me back into a functional state, but given 
all the mucking I think I’ll restore a clean FS again anyway.

Thanks again for your help.

        Zach

Attachment: smime.p7s
Description: S/MIME cryptographic signature

<Prev in Thread] Current Thread [Next in Thread>