On 10/2/2022 5:38 PM, Jon LaBadie wrote:
On Sun, Oct 02, 2022 at 04:52:24PM -0400, Bill Cunningham wrote:
I wanted to ask all who might be interested too, and know the
answers to this, first, in short,
...
And also what comes goes, my system went down and no worries. But I
did try to rescue the system with e2fsck. When done after quite some
time. All the showed up was 'lost+found' and in that directory was a lot
of directories that were numbered. Some had the hash in front. I guess I
really did a number on it. Nothing was lost worth keeping. It needed
cleaned anyway.
I'm surprised all of then did not begin with the octothorpe (#).
Fsck puts things into the lost+found directory that appear to be
properly allocated files, i.e. have an allocated inode and allocated
data blocks, but which lack any entry in any directory to access
them by name.
The number is typically the inode number.
As admin you would be able to examine the directories and files
under lost+found and perhaps determine where they were originally
and whether you should move them back there. Their owner and
group haven't changed so they may give you clues. The file(1)
command may tell you their file types for non-text files.
Although you say nothing valuable was lost, you may wish to
check the l+f files anyway just to be sure.
Jon
I really didn't know what to do with it as the next step. I didn't know
if the filesystem was ruined or not. I just reformatted and reinstalled.
If I could've got a working system back up, I would've. Was there any
fixing to this? This happened, I believe, with a typed mismatch to e2image.
e2image -raO <number> /dev/sda3 file.e2i | cp --always=sparse
I believe the error here was not using "-" as the output for the pipe to
cp. I also used "/dev/sda3" as the copied directory and was doing this
from the unmounted /dev/sda via a usb RO mount. I also might have forgot
the redirect ">" into a file. I have never used e2image before so I
should've used fsarchiver or dump on a mounted system. I wanted to and
believed I did, copy to another partition but evidently overwrote my
filesystem.
The <number> here was the number in the man e2image to make enough room
for a partition table.
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
