Arch Linux

violagirl23

Member

Registered: 2008-01-24

Posts: 184

fsck.ext3 a little too fast, what's best way make sure nothing lost?

Short of reinstalling, what are the easiest measures I can take to make sure what I can guarentee is not corrupted is not corrupted? I am going to resync pacman and reinstall everything on my system, but is there anything else I can do? I went through that fsck.ext3 a LITTLE too fast (the system refused to boot until I did it) and now fear something important might have been written. There *are* two files in lostandfound, though I'm not quite sure what to do with them. I guess I'm just a little concerned. All *seems* to be well but...... yeah.
I think I found at least one thing that is corrupt... cd! When you put cd <path that doesn't exist> it spits out weird symbols instead of the usual error message:

megini /  $ cd De
bash: cd: De: Τ褦ʥեǥ쥯ȥϤޤ

Is that a part of coreutils?

Last edited by violagirl23 (2008-06-18 07:14:12)

---

"You can't just ask to borrow somebody else's lampshade. It's AWKWARD!"

sniffles

Member

Registered: 2008-01-23

Posts: 275

Re: fsck.ext3 a little too fast, what's best way make sure nothing lost?

How did you run fsck?

Misfit138

Misfit Emeritus

From: USA

Registered: 2006-11-27

Posts: 4,189

Re: fsck.ext3 a little too fast, what's best way make sure nothing lost?

..and yes cd is part of coreutils.

---

Amiga 1000 restomod
IBM PCjr restomod
C=64 restodmod
Sauengard

Lachkater

Member

From: Germany

Registered: 2008-02-04

Posts: 40

Re: fsck.ext3 a little too fast, what's best way make sure nothing lost?

looking into the two files (sudo cat /lost+found/*) might be a good idea.

Dheart

Member

From: Sofia, Bulgaria

Registered: 2006-10-26

Posts: 956

Re: fsck.ext3 a little too fast, what's best way make sure nothing lost?

I think I found at least one thing that is corrupt... cd! When you put cd <path that doesn't exist> it spits out weird symbols instead of the usual error message:

megini /  $ cd De
bash: cd: De: Τ褦ʥեǥ쥯ȥϤޤ

Is that a part of coreutils?

You sure that's an issue? It looks to me that it is actually an localized terminal output of the tipical error message... And obviously the terminal can't the display the characters... What locale are you using?
Try issuing the same command in an unicode terminal like rxvt-unicode.

---

My victim you are meant to be
No, you cannot hide nor flee
You know what I'm looking for
Pleasure your torture, I will endure...

violagirl23

Member

Registered: 2008-01-24

Posts: 184

Re: fsck.ext3 a little too fast, what's best way make sure nothing lost?

I'm pretty sure the cd thing isn't a terminal issue, seeing as it worked yesterday, with no change. And my terminal (in Gnome) CAN display characters.
I did... fsck.ext3 /dev/sda3 and went through it, it kept asking me stuff and it was like gah what? (the -p flag did not work, said I HAD to run it manually).
Okay, one of the files, #3342648, is a completely empty directory (no hidden files either), and the other one, #3342657, is a file that says....

%DEPENDS%
xine-lib
curl>=7.16.2
libxtst
libxinerama
libxv
libpng
libxft
libsm
libxxf86vm

and that's it. I think. The second one looks like it has something to do with a pacman file, doesn't it?

Last edited by violagirl23 (2008-06-18 15:21:28)

---

"You can't just ask to borrow somebody else's lampshade. It's AWKWARD!"

carlocci

Member

From: Padova - Italy

Registered: 2008-02-12

Posts: 368

Re: fsck.ext3 a little too fast, what's best way make sure nothing lost?

..and yes cd is part of coreutils.

Sounds more like a bash embedded command to me!

Reinstalling bash could help

violagirl23

Member

Registered: 2008-01-24

Posts: 184

Re: fsck.ext3 a little too fast, what's best way make sure nothing lost?

After a pacman -S $(pacman -Qq | grep -v "$(pacman -Qmq)"), cd is well again. Besides figuring out where that one file in the lost&found went, is there anything else I can really do at this point, or have I done all I can?

---

"You can't just ask to borrow somebody else's lampshade. It's AWKWARD!"

retsaw

Member

From: London, UK

Registered: 2005-03-22

Posts: 132

Re: fsck.ext3 a little too fast, what's best way make sure nothing lost?

fsck doesn't normally do a full check on ext3 unless the filesystem is due a check either according to the time since the last check or the mount count, however you can force a check by using the -f option.

I would only bother reinstalling packages if I had a good reason to think their files were corrupted, e.g. weird errors like the one with the cd command, complaints about missing file or files from a package turning up in lost+found.  All packages will reinstalled sooner or later anyway when the packages get updated.

That file from lost+found looks like the pacman depends files for xine-ui, so you could just move it back to /var/lib/pacman/local/xine-ui-<version>/depends where <version> is the version you have installed on your system.

Oh, and "which cd" doesn't return a result for a file, so I think carlocci is right about it being a bash built-in.

violagirl23

Member

Registered: 2008-01-24

Posts: 184

Re: fsck.ext3 a little too fast, what's best way make sure nothing lost?

The system would not boot unless I did the fsck. It told me there were errors and it could not boot the root filesystem unless I fixed them. The -p flag failed, so it insisted I do it manually.

---

"You can't just ask to borrow somebody else's lampshade. It's AWKWARD!"

Misfit138

Misfit Emeritus

From: USA

Registered: 2006-11-27

Posts: 4,189

Re: fsck.ext3 a little too fast, what's best way make sure nothing lost?

..and yes cd is part of coreutils.

Sounds more like a bash embedded command to me!

Reinstalling bash could help

By George, you must be right!

---

Amiga 1000 restomod
IBM PCjr restomod
C=64 restodmod
Sauengard