Hard to get rid of two files
in [Shell]
|
Prev: Find error
Next: Drop '$' with sed
From: John W. Krahn on 23 Jun 2008 13:06 I've got a couple of files in lost+found that were left there after an fsck operation: -rwS--s-wT 1 1418 36752 92966795 1972-12-11 16:06 #48581751 --wSr--rw- 1 1418 34988 92965031 1972-12-11 15:37 #48582225 I've tried "rm -f" and chmod but I keep getting an "Operation not permitted" message. How can I remove these files? (Files are on an external USB mounted hard drive if that matters.) John -- Perl isn't a toolbox, but a small machine shop where you can special-order certain sorts of tools at low cost and in short order. -- Larry Wall
From: Old Man on 23 Jun 2008 13:15 John W. Krahn wrote: > I've got a couple of files in lost+found that were left there after an > fsck operation: > > -rwS--s-wT 1 1418 36752 92966795 1972-12-11 16:06 #48581751 > --wSr--rw- 1 1418 34988 92965031 1972-12-11 15:37 #48582225 > > I've tried "rm -f" and chmod but I keep getting an "Operation not > permitted" message. > > How can I remove these files? > > (Files are on an external USB mounted hard drive if that matters.) > > > John You might try "rm -i \#*" and read the interactive messages very carefully before entering a response. If that doesn't work, "rm -i *", and put your finger on the "q" key just in case you get key happy. It wouldn't hurt a bit to be either the file owner or the root user. If you don't have an oops key, run your recorder to capture the massive crying and screaming because the messages were not carefully read before typing. Old Man
From: John W. Krahn on 23 Jun 2008 14:00 Old Man wrote: > John W. Krahn wrote: >> I've got a couple of files in lost+found that were left there after an >> fsck operation: >> >> -rwS--s-wT 1 1418 36752 92966795 1972-12-11 16:06 #48581751 >> --wSr--rw- 1 1418 34988 92965031 1972-12-11 15:37 #48582225 >> >> I've tried "rm -f" and chmod but I keep getting an "Operation not >> permitted" message. >> >> How can I remove these files? >> >> (Files are on an external USB mounted hard drive if that matters.) > > You might try "rm -i \#*" and read the interactive messages > very carefully before entering a response. > > If that doesn't work, "rm -i *", and put your finger on the "q" > key just in case you get key happy. "rm -i" doesn't help, I just get the message "Operation not permitted". > It wouldn't hurt a bit to be either the file owner or the root user. I am trying this as root. John -- Perl isn't a toolbox, but a small machine shop where you can special-order certain sorts of tools at low cost and in short order. -- Larry Wall
From: Bill Marcum on 23 Jun 2008 14:34 On 2008-06-23, John W. Krahn <someone(a)example.com> wrote: > > > Old Man wrote: >> John W. Krahn wrote: >>> I've got a couple of files in lost+found that were left there after an >>> fsck operation: >>> >>> -rwS--s-wT 1 1418 36752 92966795 1972-12-11 16:06 #48581751 >>> --wSr--rw- 1 1418 34988 92965031 1972-12-11 15:37 #48582225 >>> >>> I've tried "rm -f" and chmod but I keep getting an "Operation not >>> permitted" message. >>> >>> How can I remove these files? >>> >>> (Files are on an external USB mounted hard drive if that matters.) >> >> You might try "rm -i \#*" and read the interactive messages >> very carefully before entering a response. >> >> If that doesn't work, "rm -i *", and put your finger on the "q" >> key just in case you get key happy. > > "rm -i" doesn't help, I just get the message "Operation not permitted". > Make sure the drive isn't mounted read-only, although if it is you should get a "read-only filesystem" error message. You might try fsck again. Remember to umount the drive first, and use "fsck -f" to check the file system even if it seems to be clean. > >> It wouldn't hurt a bit to be either the file owner or the root user. > > I am trying this as root. > > > > John
From: Todd H. on 23 Jun 2008 14:52
"John W. Krahn" <someone(a)example.com> writes: > I've got a couple of files in lost+found that were left there after an > fsck operation: > > -rwS--s-wT 1 1418 36752 92966795 1972-12-11 16:06 #48581751 > --wSr--rw- 1 1418 34988 92965031 1972-12-11 15:37 #48582225 What the heck is the T file mode in this context? I assume it's something to do with a sticky bit, but its impact I'm not sure? Root should be able to wack these. Otherwise, you can create userid that have those UID's and use that user to try to delete them with those users. But root should be able to wack anything...shouldn't it? What file system is in use by the external drive? -- Todd H. http://www.toddh.net/ |