On Fri, Jan 8, 2021 at 4:42 AM Sreyan Chakravarty <sreyan32(a)gmail.com> wrote:
Is there an fsck fix available for my problem ?
Yes it just got done.
Can my filesystem be fixed? Or do I have to erase everything and do a
reinstall ?
Strong likelihood that it can be fixed. But if the user data is
important we should do a btrfs restore first. That's a safe read-only
operation, does not change the file system like fsck which always has
risk.
Also is the fix for my particular problem being worked on by the
devs
at the particular moment ?
Yes.
Are we living that close to the edge ?
It's actually an unusual failure, so it is an edge case. I'm happy to
discuss this part later. Priority is to get your data backed up, and
fix the file system.
> You could add -x -m to this if you want.
>
Wait didn't you just say -x and -m will give errors. I don't
understand what you mean by "-m and -x require files to be restored
first or you get additional errors."
-m and -x only get applied after files are restored. The files are
extracted and saved. And then the metadata/xattr is applied to the
files.
-D prevents the files from being restored. It's a dry run. Since
there's no files, -m -x results in errors.
If you want I am available on US time but only if you let me know in
advance.
I saw your message today on IRC and replied about 15 seconds later but
didn't get a reply. Anyway, next email I'll write up a procedure.
--
Chris Murphy