[lug] cruft from an fsck'ed partition

D. Stimits stimits at idcomm.com
Thu Jun 21 14:09:09 MDT 2001


Hugh Brown wrote:
> 
> I have been doing a tar over ssh backup of a filesystem to a disk.  Too
> often it dies and complains about a corrupted MAC on input.  Too many times
> I have had to go through lengthy fsck's the next time it comes up.
> 
> Today on that disk I found a copy of the lost+found folder from the
> original system but it was magically a block special device instead of a
> regular folder.
> 
> br-xr---wx    2 26723    19443     69,  49 Sep 20  2005 lost+found

Definitely it should be a directory.

> 
> Here's what I have tried while su -'ed to root:
> 
> $ rm lost\+found
> rm: remove `lost+found'? y
> rm: cannot unlink `lost+found': Operation not permitted

I think removing lost+found might be a bad idea anyway. You should try
the command "mklost+found" (see man page).

> 
> $ chown root lost+found
> chown: lost+found: Operation not permitted
> 
> $ lsattr lost+found
> lsattr: No such device While reading flags on lost+found
> 
> $ mv lost+found /tmp
> mv: cannot unlink `lost+found': Operation not permitted
> mv: cannot remove `lost+found': Operation not permitted
> 
> I was able to remove the copy in /tmp though
> 
> I tried adding a user with uid 26723 and then repeated the same commands
> and got nowhere.  In /var/log/messages I have
> 
> Jun 21 15:38:09 localhost modprobe: modprobe: Can't locate module block-major-69

This appears to be scsi devices starting with "sdc", owner root, group
disk. Check out /dev/MAKEDEV for recreation.

D. Stimits, stimits at idcomm.com

> 
> Any ideas?
> 
> Hugh
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug



More information about the LUG mailing list