On Sun, Jan 3, 2021 at 9:30 PM André Isidro da Silva <[email protected]> wrote: > > I might be in some panic, I'm sorry for the info I'm not experienced > enough to give. > > I was in a live iso trying really hard to repair my root btrfs from > which I had used all the space avaiable.. I was trying to move a /usr > partition into the btrfs system, but I didn't check the space available > with the tool, instead used normal tools, because I didn't understand or > actually thought about how the subvolumes would change... sorry this > isn't even the issue anymore; to move /usr I had a temporary /usr copy > in another btrfs system (my /home data partition) and so mounted both > partitions. However this was done in a linux "boot fail console" from > which I didn't know how to proper shutdown.. so I eventually forced the > shutdown withou umounting stuff (...), I think that forced shutdown > might have broken the second partition that now isn't recognized with > btrfs check or mountable. It might also have happen when using the live > iso, but the forced shutdown seemed more likely, since I did almost no > operations but mount/cp. This partition was my data partition, I thought > it was safe to use for this process, since I was just copying files from > it. I do have a backup, but it's old so I'll still lose a lot.. help.
First, make no changes, attempt no repairs. Next save history of what you did. A forced shutdown does not make Btrfs unreadable, although if writes are happening at the time of the shutdown and the drive firmware doesn't properly honor write order, then it might be 'btrfs restore' territory. What do you get for: btrfs filesystem show kernel messages (dmesg) that appear when you try to mount the volume but it fails. -- Chris Murphy
