Re: cleaning up lost+found

2000-07-26 Thread Petr \[Dingo\] Dvorak
Hey list, problem solved, and this is the trick what Peter Galbraith sent me: cr-Srw-r--1 2540229706115, 58 Oct 9 1999 fontsmpl.sty debugfs -w -R "rm /lost+found/bad_device/fontsmpl.sty" /dev/hda1 Thanks to all for all your help!

Re: cleaning up lost+found

2000-07-26 Thread Bob McGowan
Once upon a time, when I was working with UNIX version 7, I had a case where I could not clean up a disk using fsck. I used a program called (as I remember) 'clri' to wipe out the inode, then did an fsck to clean up the "orphans" that I had created. 'clri' doesn't exist anymore, that I know of (f

Re: cleaning up lost+found

2000-07-26 Thread Olaf Meeuwissen
"Petr [Dingo] Dvorak" <[EMAIL PROTECTED]> writes: > On Wed, 26 Jul 2000, Lehel Bernadt wrote: > > LB> On 26-Jul-2000 Olaf Meeuwissen wrote: > > -- snip -- > > OM> in /home/lost+found that I can't seems to remove. Not even as root! > > -- snip -- > > LB> They probably have the immutable attri

RE: cleaning up lost+found

2000-07-26 Thread Petr \[Dingo\] Dvorak
On Wed, 26 Jul 2000, Lehel Bernadt wrote: LB> On 26-Jul-2000 Olaf Meeuwissen wrote: -- snip -- OM> in /home/lost+found that I can't seems to remove. Not even as root! -- snip -- LB> They probably have the immutable attribute set. Remove it with chattr. I have the same problem, mine happened

RE: cleaning up lost+found

2000-07-26 Thread Lehel Bernadt
On 26-Jul-2000 Olaf Meeuwissen wrote: > Debians, > > I goofed up a little while ago and connected two SCSI devices with the > same ID. I've cleaned up the mess, but now I have a number of files > in /home/lost+found that I can't seems to remove. Not even as root! > > Typical output of ls -l on