Carlos E. R. wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
>
> The Wednesday 2008-06-25 at 10:45 -0500, Moby wrote:
>
>> This is part of the ongoing saga with, what appears to be, a bug 
>> either in the kernel or reiserfs or both with OpenSuSE 11.  Fairly 
>> extensively documented at 
>> https://bugzilla.novell.com/show_bug.cgi?id=389656
>>
>> My machine has had hard crashes due to the above mentioned bug.  
>> After the last hard crash (
>> which occurred while doing rpmbuild on xorg src rpm)  , I had to run 
>> fsck. fskc reports clean now (ran it one more time just to be sure), 
>> but I am stuck with /usr/src/packages/BUILD/xxx directories that I 
>> cannot delete.  Attempts to delete those directory trees give the 
>> following error:
>>
>> cannot remove `xorg-server-1.4.2/GL': Input/output error
>>
>> Attempts to do ls -il on a directory to get the inode result in the 
>> same error.  However, I was able to mv the above-mentioned BUILD to 
>> BUILD.000.  So now it looks like the / resiferfs has corruption 
>> caused by last hard crash that is not recoverable with 
>> fsck.reiserfs.  *MAJOR SIGH*
>
> How were you fsck-ing that partition? If that is the root filesystem 
> and can not be umounted then the reiserfsck program can not do aa 
> complete job. This is different from ext3, which can be checked while 
> mounted r/o. The procedure is to run the test from a rescue system in 
> DVD (the install disk) or from another partition (ie, boooting from 
> another partition).
>
> - -- Cheers,
>        Carlos E. R.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.4-svn0 (GNU/Linux)
>
> iD8DBQFIYoPetTMYHG2NR9URAveHAJwM3y3b5jYTEaOFxSirFBn06Nba1QCghGTi
> JMLZ466nlsxzmSQFueiOVak=
> =QHQb
> -----END PGP SIGNATURE-----
Steps for fsck:
1) Boot to single-user mode:
init 1

2)  Remount root as Ro:
mount -remount,ro /

3)  Do fsck:
fsck.resiserfs --fix-fixable --rebuild-tree /dev/

The fsck ran fine and the reason I say so is because it did claim to 
have found and fixed various inconsistencies, in addition to giving me 
some stuff in /lost+found.

The undeleteable directory trees, as I mentioned in a subsequent post on 
the list, turned to be entries with corrupted uid's and gid's.  Doing 
chown one by one from the top down allowed me to finally delete them.  
The bad uid and gids where low integers, 200+ (such as 286, 256 etc).

-- 
--Moby

They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.  -- Benjamin Franklin


-- 
To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

The Wednesday 2008-06-25 at 13:17 -0500, Moby wrote:

Carlos E. R. wrote:

...

...

How were you fsck-ing that partition? If that is the root filesystem and can not be umounted then the reiserfsck program can not do aa complete job. This is different from ext3, which can be checked while mounted r/o. The procedure is to run the test from a rescue system in DVD (the install disk) or from another partition (ie, boooting from another partition).

...

Steps for fsck: 1) Boot to single-user mode: init 1

2) Remount root as Ro: mount -remount,ro /

3) Do fsck: fsck.resiserfs --fix-fixable --rebuild-tree /dev/<path to root device>

I know, that procedure works fine with ext3, but not with reiserfs, or not always. I know, I have been bitten with that problem in the past. You need to boot the dvd or another partition as rescue system.

...

The fsck ran fine and the reason I say so is because it did claim to have found and fixed various inconsistencies, in addition to giving me some stuff in /lost+found.

The undeleteable directory trees, as I mentioned in a subsequent post on the list, turned to be entries with corrupted uid's and gid's. Doing chown one by one from the top down allowed me to finally delete them. The bad uid and gids where low integers, 200+ (such as 286, 256 etc).

Weird.

If you were trying to remove the files as user, yes. But the problem with this type of reiserfs corruption is that even root is denied access. I don't remember if you said you tried as root :-?

- -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQFIYo2dtTMYHG2NR9URAmB6AKCXw0gD+7SKW+lFiB47GB+i7QcP2QCeJYHV yx3RRXxKL/9wYKfqnvo9R+8= =AYXK -----END PGP SIGNATURE----- I was doing all the above steps, including the attempted deletes, as root. Yes, weird indeed, but I have a feeling there are a few more hair-loss inducing weirdnesses with OpenSuSE 11 waiting in the dark shadows. I think one just hit me - XVnc using 100% cpu. I have sketchy

Carlos E. R. wrote: details on that one at this time, but I will start a new thread once I get enough data. -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

...

...

I was doing all the above steps, including the attempted deletes, as root. Yes, weird indeed, but I have a feeling there are a few more hair-loss inducing weirdnesses with OpenSuSE 11 waiting in the dark shadows. I think one just hit me - XVnc using 100% cpu. I have sketchy details on that one at this time, but I will start a new thread once I get enough data.

The undeletable files as root in reiserfs is a years old problem, and the known solution is to fsck from the DVD.

- -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQFIYpKRtTMYHG2NR9URAnL6AKCJGmVjkpu/sFQ+msQHbW2fMVsJwACfcNHm k22Mtz7dHYvOrECBwMFF8AA= =1Fq7 -----END PGP SIGNATURE----- Oh ok - good to know. Thanks Carlos.

-- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org