[opensuse] I can not delete some files and directories.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have a Linux based multimedia box (not openSUSE), to which I connect via telnet. It has an external hard disk via usb, formatted as ext2 (2, not 3 nor 4). It runs kernel 2.4.21-xfs, and BusyBox v1.01 (2006.11.30-16:43+0000). As the disk is connected via usb, I can, when not in use, connect it to my openSUSE machine. I use that sometimes for maintenance of the disk. Other times, I use the fsck facility on the machine itself. After one of these runs, I found some files on the lost+found directory; I copied them to my openSUSE machine via ftp, for later inspection, then attempted to delete them on the machine. FTP (with 'mc') deleted most, but not all. Looking via telnet, I see very strange permissions: [root@Moria:/usb/lost+found]# ls -l - ---xr-S--t 1 -2099230 16108097 36864 May 24 1985 #4047692 drw-rw---T 2 -2069826 10738976 40960 Jul 11 2036 #4048177 d-wxrw-r-x 2 11331111 3129454 45056 Aug 18 1969 #4049358 - ---sr----T 1 82196912 10913612 49152 May 22 1990 #4049402 drwxr-s--T 2 -2128562 -1594398 45056 May 13 1970 #4065600 - ---x--x-w- 1 79724563 23907546 40960 Dec 26 1974 #4066597 - ---Sr---wt 1 14976932 -2813512 45056 Feb 9 1902 #4079810 - --w-rwxr-x 1 -7658286 -2018176 49152 Feb 18 1971 #4083190 dr--r-s--T 2 85894704 85786717 36864 Sep 10 1948 #4083819 [root@Moria:/usb/lost+found]# rmdir \#4065600/ rmdir: `#4065600/': Operation not permitted [root@Moria:/usb/lost+found]# I'm not familiar with those permissions. But I can not delete them. I can not change the permissions either: [root@Moria:/usb/lost+found]# rmdir \#4065600/ rmdir: `#4065600/': Operation not permitted [root@Moria:/usb/lost+found]# chmod u+r+w \#4065600/ chmod: #4065600/: Operation not permitted [root@Moria:/usb/lost+found]# chown root \#4065600/ chown: #4065600/: Operation not permitted [root@Moria:/usb/lost+found]# The current permissions are: drwxr-s--T 2 -2128562 -1594398 45056 May 13 1970 #4065600 How can I delete those files? What means the 'T' and 't' attributes? Ideas? Of course, I'll try, when the device is not needed, to connect the disk to openSUSE and try from here, to see if things are different :-? - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlPBqEsACgkQtTMYHG2NR9X/fQCfTclCwuYIb4IoGKYxePUF00OZ OiwAoI0qyHBMj+cPPLar7TXsDPiUgKXa =vxWe -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zaterdag 12 juli 2014 23:27:32 schreef Carlos E. R.:
Hi,
I have a Linux based multimedia box (not openSUSE), to which I connect via telnet. It has an external hard disk via usb, formatted as ext2 (2, not 3 nor 4). It runs kernel 2.4.21-xfs, and BusyBox v1.01 (2006.11.30-16:43+0000).
As the disk is connected via usb, I can, when not in use, connect it to my openSUSE machine. I use that sometimes for maintenance of the disk.
Other times, I use the fsck facility on the machine itself. After one of these runs, I found some files on the lost+found directory; I copied them to my openSUSE machine via ftp, for later inspection, then attempted to delete them on the machine. FTP (with 'mc') deleted most, but not all.
Looking via telnet, I see very strange permissions:
[root@Moria:/usb/lost+found]# ls -l ---xr-S--t 1 -2099230 16108097 36864 May 24 1985 #4047692 drw-rw---T 2 -2069826 10738976 40960 Jul 11 2036 #4048177 d-wxrw-r-x 2 11331111 3129454 45056 Aug 18 1969 #4049358 ---sr----T 1 82196912 10913612 49152 May 22 1990 #4049402 drwxr-s--T 2 -2128562 -1594398 45056 May 13 1970 #4065600 ---x--x-w- 1 79724563 23907546 40960 Dec 26 1974 #4066597 ---Sr---wt 1 14976932 -2813512 45056 Feb 9 1902 #4079810 --w-rwxr-x 1 -7658286 -2018176 49152 Feb 18 1971 #4083190 dr--r-s--T 2 85894704 85786717 36864 Sep 10 1948 #4083819 [root@Moria:/usb/lost+found]# rmdir \#4065600/ rmdir: `#4065600/': Operation not permitted [root@Moria:/usb/lost+found]#
I'm not familiar with those permissions. But I can not delete them. I can not change the permissions either:
[root@Moria:/usb/lost+found]# rmdir \#4065600/ rmdir: `#4065600/': Operation not permitted [root@Moria:/usb/lost+found]# chmod u+r+w \#4065600/ chmod: #4065600/: Operation not permitted [root@Moria:/usb/lost+found]# chown root \#4065600/ chown: #4065600/: Operation not permitted [root@Moria:/usb/lost+found]#
The current permissions are:
drwxr-s--T 2 -2128562 -1594398 45056 May 13 1970 #4065600
How can I delete those files?
What means the 'T' and 't' attributes?
These are sticky bits, see command "info coreutils 'ls invocation'"
Ideas?
Of course, I'll try, when the device is not needed, to connect the disk to openSUSE and try from here, to see if things are different :-?
searching for stickky bit may come up with some answers. -- fr.gr. Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-07-12 23:55, Freek de Kruijf wrote:
Op zaterdag 12 juli 2014 23:27:32 schreef Carlos E. R.:
What means the 'T' and 't' attributes?
These are sticky bits, see command "info coreutils 'ls invocation'"
Ah, ok, thanks, found a nice list: File: coreutils.info, Node: What information is listed, The file type is one of the following characters: `-' regular file `b' block special file `c' character special file `C' high performance ("contiguous data") file `d' directory `D' door (Solaris 2.5 and up) `l' symbolic link `M' off-line ("migrated") file (Cray DMF) `n' network special file (HP-UX) `p' FIFO (named pipe) `P' port (Solaris 10 and up) `s' socket `?' some other file type The file mode bits listed are similar to symbolic mode specifications (*note Symbolic Modes::). But `ls' combines multiple bits into the third character of each set of permissions as follows: `s' If the set-user-ID or set-group-ID bit and the corresponding executable bit are both set. `S' If the set-user-ID or set-group-ID bit is set but the corresponding executable bit is not set. `t' If the restricted deletion flag or sticky bit, and the other-executable bit, are both set. The restricted deletion flag is another name for the sticky bit. *Note Mode Structure::. `T' If the restricted deletion flag or sticky bit is set but the other-executable bit is not set. `x' If the executable bit is set and none of the above apply. `-' Otherwise. Following the file mode bits is a single character that specifies whether an alternate access method such as an access control list applies to the file. When the character following the file mode bits is a space, there is no alternate access method. When it is a printing character, then there is such a method. GNU `ls' uses a `.' character to indicate a file with an SELinux security context, but no other alternate access method. A file with any other combination of alternate access methods is marked with a `+' character.
Ideas?
Of course, I'll try, when the device is not needed, to connect the disk to openSUSE and try from here, to see if things are different :-?
searching for stickky bit may come up with some answers.
Sticky! I did not remember that the 't' stood for "sticky". but no, I can not remove that bit either. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Freek de Kruijf wrote:
Op zaterdag 12 juli 2014 23:27:32 schreef Carlos E. R.:
Hi,
I have a Linux based multimedia box (not openSUSE), to which I connect via telnet. It has an external hard disk via usb, formatted as ext2 (2, not 3 nor 4). It runs kernel 2.4.21-xfs, and BusyBox v1.01 (2006.11.30-16:43+0000).
As the disk is connected via usb, I can, when not in use, connect it to my openSUSE machine. I use that sometimes for maintenance of the disk.
Other times, I use the fsck facility on the machine itself. After one of these runs, I found some files on the lost+found directory; I copied them to my openSUSE machine via ftp, for later inspection, then attempted to delete them on the machine. FTP (with 'mc') deleted most, but not all.
Looking via telnet, I see very strange permissions:
[root@Moria:/usb/lost+found]# ls -l ---xr-S--t 1 -2099230 16108097 36864 May 24 1985 #4047692 drw-rw---T 2 -2069826 10738976 40960 Jul 11 2036 #4048177 d-wxrw-r-x 2 11331111 3129454 45056 Aug 18 1969 #4049358 ---sr----T 1 82196912 10913612 49152 May 22 1990 #4049402 drwxr-s--T 2 -2128562 -1594398 45056 May 13 1970 #4065600 ---x--x-w- 1 79724563 23907546 40960 Dec 26 1974 #4066597 ---Sr---wt 1 14976932 -2813512 45056 Feb 9 1902 #4079810 --w-rwxr-x 1 -7658286 -2018176 49152 Feb 18 1971 #4083190 dr--r-s--T 2 85894704 85786717 36864 Sep 10 1948 #4083819 [root@Moria:/usb/lost+found]# rmdir \#4065600/ rmdir: `#4065600/': Operation not permitted [root@Moria:/usb/lost+found]#
I'm not familiar with those permissions. But I can not delete them. I can not change the permissions either:
[root@Moria:/usb/lost+found]# rmdir \#4065600/ rmdir: `#4065600/': Operation not permitted [root@Moria:/usb/lost+found]# chmod u+r+w \#4065600/ chmod: #4065600/: Operation not permitted [root@Moria:/usb/lost+found]# chown root \#4065600/ chown: #4065600/: Operation not permitted [root@Moria:/usb/lost+found]#
The current permissions are:
drwxr-s--T 2 -2128562 -1594398 45056 May 13 1970 #4065600
How can I delete those files?
What means the 'T' and 't' attributes?
These are sticky bits, see command "info coreutils 'ls invocation'"
Ideas?
Of course, I'll try, when the device is not needed, to connect the disk to openSUSE and try from here, to see if things are different :-?
searching for stickky bit may come up with some answers.
see also: man 1 chmod man 2 chmod The section 1 manual page describes the command and how to change mode bits the section 2 manpage describes the kernel call of the same name, and gives a more in depth description of what the mode bits do. see also man 2 unlink ERRORS EPERM -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/12/2014 04:27 PM, Carlos E. R. wrote:
[root@Moria:/usb/lost+found]# ls -l ---xr-S--t 1 -2099230 16108097 36864 May 24 1985 #4047692 drw-rw---T 2 -2069826 10738976 40960 Jul 11 2036 #4048177 d-wxrw-r-x 2 11331111 3129454 45056 Aug 18 1969 #4049358 ---sr----T 1 82196912 10913612 49152 May 22 1990 #4049402 drwxr-s--T 2 -2128562 -1594398 45056 May 13 1970 #4065600 ---x--x-w- 1 79724563 23907546 40960 Dec 26 1974 #4066597 ---Sr---wt 1 14976932 -2813512 45056 Feb 9 1902 #4079810 --w-rwxr-x 1 -7658286 -2018176 49152 Feb 18 1971 #4083190 dr--r-s--T 2 85894704 85786717 36864 Sep 10 1948 #4083819 [root@Moria:/usb/lost+found]# rmdir \#4065600/ rmdir: `#4065600/': Operation not permitted [root@Moria:/usb/lost+found]#
I'm not familiar with those permissions. But I can not delete them. I can not change the permissions either:
I'm interested in the answer as well. It doesn't look like complete files are being listed, but rather some arbitrary blocks of data somehow crammed into filenames #wwxxyyzz with some really interesting dates. Was your busybox machine really running in 1902? (Picked up in horse & wagon?) - -- David C. Rankin, J.D.,P.E. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlPBru0ACgkQZMpuZ8CyrcgV0QCeOdIiDfAz5xu4Die1XKn0A3VW 8DMAn3NByWwD7A18KOrP5RC/7Sj9dBFj =gS/h -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-07-12 23:55, David C. Rankin wrote:
On 07/12/2014 04:27 PM, Carlos E. R. wrote:
I'm not familiar with those permissions. But I can not delete them. I can not change the permissions either:
I'm interested in the answer as well. It doesn't look like complete files are being listed, but rather some arbitrary blocks of data somehow crammed into filenames #wwxxyyzz with some really interesting dates. Was your busybox machine really running in 1902? (Picked up in horse & wagon?)
The files are real enough, but the metadata is wrong. There was a power failure (I pulled the cord) and some files got corrupted entries. On recovery, fsck tried to recover those, and created those strange entries. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2014-07-12 23:27 (GMT+0200) Carlos E. R. composed:
I have a Linux based multimedia box (not openSUSE), to which I connect via telnet. It has an external hard disk via usb, formatted as ext2 (2, not 3 nor 4). It runs kernel 2.4.21-xfs, and BusyBox v1.01 (2006.11.30-16:43+0000).
As the disk is connected via usb, I can, when not in use, connect it to my openSUSE machine. I use that sometimes for maintenance of the disk.
Other times, I use the fsck facility on the machine itself. After one of these runs, I found some files on the lost+found directory; I copied them to my openSUSE machine via ftp, for later inspection, then attempted to delete them on the machine. FTP (with 'mc') deleted most, but not all.
Looking via telnet, I see very strange permissions:
[root@Moria:/usb/lost+found]# ls -l - ---xr-S--t 1 -2099230 16108097 36864 May 24 1985 #4047692 drw-rw---T 2 -2069826 10738976 40960 Jul 11 2036 #4048177 d-wxrw-r-x 2 11331111 3129454 45056 Aug 18 1969 #4049358 - ---sr----T 1 82196912 10913612 49152 May 22 1990 #4049402 drwxr-s--T 2 -2128562 -1594398 45056 May 13 1970 #4065600 - ---x--x-w- 1 79724563 23907546 40960 Dec 26 1974 #4066597 - ---Sr---wt 1 14976932 -2813512 45056 Feb 9 1902 #4079810 - --w-rwxr-x 1 -7658286 -2018176 49152 Feb 18 1971 #4083190 dr--r-s--T 2 85894704 85786717 36864 Sep 10 1948 #4083819 [root@Moria:/usb/lost+found]# rmdir \#4065600/ rmdir: `#4065600/': Operation not permitted [root@Moria:/usb/lost+found]#
I'm not familiar with those permissions. But I can not delete them. I can not change the permissions either:
[root@Moria:/usb/lost+found]# rmdir \#4065600/ rmdir: `#4065600/': Operation not permitted [root@Moria:/usb/lost+found]# chmod u+r+w \#4065600/ chmod: #4065600/: Operation not permitted [root@Moria:/usb/lost+found]# chown root \#4065600/ chown: #4065600/: Operation not permitted [root@Moria:/usb/lost+found]#
The current permissions are:
drwxr-s--T 2 -2128562 -1594398 45056 May 13 1970 #4065600
How can I delete those files?
I think I have almost the exact same problem on multiple settop boxes (with slightly newer kernels than yours) on occasion, normally trying to copy over existing files, not trying to delete. I login on the STB and delete the existing files MC gets hung on using Telnet, and after deleting that way, put or copy the files with MC. This may be a question best posed to the MC user list.
What means the 'T' and 't' attributes?
http://en.wikipedia.org/wiki/Sticky_bit -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-07-13 00:06, Felix Miata wrote:
On 2014-07-12 23:27 (GMT+0200) Carlos E. R. composed:
How can I delete those files?
I think I have almost the exact same problem on multiple settop boxes (with slightly newer kernels than yours) on occasion, normally trying to copy over existing files, not trying to delete. I login on the STB and delete the existing files MC gets hung on using Telnet, and after deleting that way, put or copy the files with MC.
This may be a question best posed to the MC user list.
It does not matter, I can not delete those files via command line.
What means the 'T' and 't' attributes?
Ah, yes, sticky. Well, I can not find a combination to remove that bit, either. [root@Moria:/usb/lost+found]# chmod a-t \#4065600/ chmod: #4065600/: Operation not permitted [root@Moria:/usb/lost+found]# chmod u-t \#4065600/ chmod: #4065600/: Operation not permitted [root@Moria:/usb/lost+found]# chmod -t \#4065600/ chmod: #4065600/: Operation not permitted [root@Moria:/usb/lost+found]# [root@Moria:/usb/lost+found]# chmod 0777 \#4065600 chmod: #4065600: Operation not permitted [root@Moria:/usb/lost+found]# chmod 0777 \#4065600 I don't know if I'm using the command correctly, or there is something else. The error message says that I'm not allowed to do it, not that the syntax is wrong. Of course, as the file does not belong to 'root', nor to any listed user or group, it is a complication. drwxr-s--T 2 -2128562 -1594398 45056 May 13 1970 #4065600 -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2014-07-13 00:29 (GMT+0200) Carlos E. R. composed:
I can not delete those files via command line.
What about a recursive rmdir on the parent dir, or a mv to /dev/null or a real location then deleting the latter? If those don't work, take the the disk out of the STB and connect directly to a PC, bypassing busybox to try with newer tools? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-07-13 00:50, Felix Miata wrote:
On 2014-07-13 00:29 (GMT+0200) Carlos E. R. composed:
I can not delete those files via command line.
What about a recursive rmdir on the parent dir, or a mv to /dev/null or a real location then deleting the latter? If those don't work, take the the disk out of the STB and connect directly to a PC, bypassing busybox to try with newer tools?
All commands fail with "Operation not permitted". The rmdir man page does not say anything about recursion. Yes, I'll certainly try connect the disk to the PC, once it ends the scheduled recordings. In one hour, I expect. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2014-07-13 01:07, Carlos E. R. wrote:
On 2014-07-13 00:50, Felix Miata wrote:
Yes, I'll certainly try connect the disk to the PC, once it ends the scheduled recordings. In one hour, I expect.
Same problem: Telcontar:/mnt/Ext/Moria2/lost+found # l total 284 ---xr-S--t 1 2195736830 1610809728 36864 May 24 1985 #4047692* drw-rw---T 2 2225140482 1073897600 40960 Jul 11 2036 #4048177/ d-wxrw-r-x 2 113311111 3129454 45056 Aug 18 1969 #4049358/ ---sr----T 1 821969126 1091361282 49152 May 22 1990 #4049402* drwxr-s--T 2 2166404463 2700568576 45056 May 13 1970 #4065600/ ---x--x-w- 1 79724563 239075460 40960 Dec 26 1974 #4066597* ---Sr---wt 1 1497693200 4013616054 45056 Feb 9 1902 #4079810* --w-rwxr-x 1 3529138678 2276790368 49152 Feb 18 1971 #4083190* dr--r-s--T 2 858947044 857867178 36864 Sep 10 1948 #4083819/ drwxr-xr-x 6 root root 20480 Jul 11 23:24 ./ drwxr-xr-x 11 root root 4096 Aug 4 2012 ../ Telcontar:/mnt/Ext/Moria2/lost+found # rm \#4065600/ rm: cannot remove ‘#4065600/’: Is a directory Telcontar:/mnt/Ext/Moria2/lost+found # rmdir \#4065600/ rmdir: failed to remove ‘#4065600/’: Operation not permitted Telcontar:/mnt/Ext/Moria2/lost+found # chown root \#4065600/ chown: changing ownership of ‘#4065600/’: Operation not permitted Telcontar:/mnt/Ext/Moria2/lost+found # chmod -t \#4065600/ chmod: changing permissions of ‘#4065600/’: Operation not permitted Telcontar:/mnt/Ext/Moria2/lost+found # I'm now running fsck on it. Being ext2, it will take a long time. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2014-07-13 02:02, Carlos E. R. wrote:
On 2014-07-13 01:07, Carlos E. R. wrote:
I'm now running fsck on it. Being ext2, it will take a long time.
Well, not that long, just 8'21". Well, no change. I can not remove the files, chown them, chmod them, nor remove the sticky bits. I can do nothing on them. Telcontar:/mnt/Ext/Moria2/lost+found # rm -R /mnt/Ext/Moria2/lost+found/ rm: cannot remove ‘/mnt/Ext/Moria2/lost+found/#4048177’: Operation not permitted rm: cannot remove ‘/mnt/Ext/Moria2/lost+found/#4049358’: Operation not permitted rm: cannot remove ‘/mnt/Ext/Moria2/lost+found/#4065600’: Operation not permitted rm: cannot remove ‘/mnt/Ext/Moria2/lost+found/#4083819’: Operation not permitted rm: cannot remove ‘/mnt/Ext/Moria2/lost+found/#4047692’: Operation not permitted rm: cannot remove ‘/mnt/Ext/Moria2/lost+found/#4049402’: Operation not permitted rm: cannot remove ‘/mnt/Ext/Moria2/lost+found/#4066597’: Operation not permitted rm: cannot remove ‘/mnt/Ext/Moria2/lost+found/#4079810’: Operation not permitted rm: cannot remove ‘/mnt/Ext/Moria2/lost+found/#4083190’: Operation not permitted Telcontar:/mnt/Ext/Moria2/lost+found # -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/12/2014 5:27 PM, Carlos E. R. wrote:
On 2014-07-13 02:02, Carlos E. R. wrote:
On 2014-07-13 01:07, Carlos E. R. wrote:
I'm now running fsck on it. Being ext2, it will take a long time.
Well, not that long, just 8'21".
Well, no change. I can not remove the files, chown them, chmod them, nor remove the sticky bits. I can do nothing on them.
Telcontar:/mnt/Ext/Moria2/lost+found # rm -R /mnt/Ext/Moria2/lost+found/ rm: cannot remove �/mnt/Ext/Moria2/lost+found/#4048177�: Operation not permitted rm: cannot remove �/mnt/Ext/Moria2/lost+found/#4049358�: Operation not permitted rm: cannot remove �/mnt/Ext/Moria2/lost+found/#4065600�: Operation not permitted rm: cannot remove �/mnt/Ext/Moria2/lost+found/#4083819�: Operation not permitted rm: cannot remove �/mnt/Ext/Moria2/lost+found/#4047692�: Operation not permitted rm: cannot remove �/mnt/Ext/Moria2/lost+found/#4049402�: Operation not permitted rm: cannot remove �/mnt/Ext/Moria2/lost+found/#4066597�: Operation not permitted rm: cannot remove �/mnt/Ext/Moria2/lost+found/#4079810�: Operation not permitted rm: cannot remove �/mnt/Ext/Moria2/lost+found/#4083190�: Operation not permitted Telcontar:/mnt/Ext/Moria2/lost+found #
I spose you've tried chattr? http://en.wikipedia.org/wiki/Chattr - -- _____________________________________ - ---This space for rent--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAlPC0V0ACgkQv7M3G5+2DLLnTwCdEOwqAHT9qXMOufFhweHjIMnD kzIAn3YkQwJdoeVo4DJm2YlTF5e2MftN =dM3f -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 13/07/2014 20:35, John Andersen a écrit :
I spose you've tried chattr? http://en.wikipedia.org/wiki/Chattr
"apropos" is a sh command pretty usefull. it looks the man page titles for the argument "apropos attr" gives lot of infos on what are and what use attributes (much more than I expected :-) jdd -- http://www.dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 7/13/2014 12:08 PM, jdd wrote:
Le 13/07/2014 20:35, John Andersen a �crit :
I spose you've tried chattr? http://en.wikipedia.org/wiki/Chattr
"apropos" is a sh command pretty usefull. it looks the man page titles for the argument
"apropos attr" gives lot of infos on what are and what use attributes (much more than I expected :-)
jdd
some of us old farts just use man -k -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/13/2014 03:13 PM, John Andersen pecked at the keyboard and wrote:
On 7/13/2014 12:08 PM, jdd wrote:
Le 13/07/2014 20:35, John Andersen a �crit :
I spose you've tried chattr? http://en.wikipedia.org/wiki/Chattr
"apropos" is a sh command pretty usefull. it looks the man page titles for the argument
"apropos attr" gives lot of infos on what are and what use attributes (much more than I expected :-)
jdd
some of us old farts just use man -k
I may be old but my farts aren't. :-) -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/12/2014 06:50 PM, Felix Miata pecked at the keyboard and wrote:
On 2014-07-13 00:29 (GMT+0200) Carlos E. R. composed:
I can not delete those files via command line.
What about a recursive rmdir on the parent dir, or a mv to /dev/null or a real location then deleting the latter? If those don't work, take the the disk out of the STB and connect directly to a PC, bypassing busybox to try with newer tools?
Sometimes when I have problem files I'll try using rm -ri for recursive/interactive remove. Doesn't work all the time but it is worth a shot. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 07/12/2014 05:27 PM, Carlos E. R. wrote:
Hi,
[snip]
Looking via telnet, I see very strange permissions:
[root@Moria:/usb/lost+found]# ls -l ---xr-S--t 1 -2099230 16108097 36864 May 24 1985 #4047692 drw-rw---T 2 -2069826 10738976 40960 Jul 11 2036 #4048177 d-wxrw-r-x 2 11331111 3129454 45056 Aug 18 1969 #4049358 ---sr----T 1 82196912 10913612 49152 May 22 1990 #4049402 drwxr-s--T 2 -2128562 -1594398 45056 May 13 1970 #4065600 ---x--x-w- 1 79724563 23907546 40960 Dec 26 1974 #4066597 ---Sr---wt 1 14976932 -2813512 45056 Feb 9 1902 #4079810 --w-rwxr-x 1 -7658286 -2018176 49152 Feb 18 1971 #4083190 dr--r-s--T 2 85894704 85786717 36864 Sep 10 1948 #4083819 [root@Moria:/usb/lost+found]# rmdir \#4065600/ rmdir: `#4065600/': Operation not permitted [root@Moria:/usb/lost+found]#
I'm not familiar with those permissions. But I can not delete them. I can not change the permissions either:
[root@Moria:/usb/lost+found]# rmdir \#4065600/ rmdir: `#4065600/': Operation not permitted [root@Moria:/usb/lost+found]# chmod u+r+w \#4065600/ chmod: #4065600/: Operation not permitted [root@Moria:/usb/lost+found]# chown root \#4065600/ chown: #4065600/: Operation not permitted [root@Moria:/usb/lost+found]#
The current permissions are:
drwxr-s--T 2 -2128562 -1594398 45056 May 13 1970 #4065600
How can I delete those files?
What means the 'T' and 't' attributes?
Ideas?
BTDT.
What you have is corrupted inodes.
The 'ls' command is trying its best to interpret the random bit patterns
of the inodes. Its mapping the random junk there into what *you*
interpret as various status bit according to the manual page.
But really they are just nonsense. That is why you cannot delete
anything. It's all corrupt.
Look, the information is supposed to be
<mode>, <# of links>, <owner>, <group>, <size>,
dr--r-s--T 2 85894704 85786717 36864 Sep 10 1948 #4083819
So you have ownerUID=85894704 and a date in 1948 with epoch 1970? So it must be a -ve number. Is this all not a hint? It really doesn't matter what the 'T' and 't' attributes are, or the 'S' and 's' or even the 'r', 'w', and 'x' since this is all just random stuff. Like I said, BTDT. What I did was went in with a low level binary editor and cleared out the inodes. Difficult and hairy stuff. I think there are other tools now, over and above fsck. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-07-13 02:13, Anton Aylward wrote:
On 07/12/2014 05:27 PM, Carlos E. R. wrote:
Ideas?
BTDT.
Huh? Ah: cer@Telcontar:~> wtf BTDT BTDT: been there, done that cer@Telcontar:~>
What you have is corrupted inodes. The 'ls' command is trying its best to interpret the random bit patterns of the inodes. Its mapping the random junk there into what *you* interpret as various status bit according to the manual page. But really they are just nonsense. That is why you cannot delete anything. It's all corrupt.
That /does/make sense.
It really doesn't matter what the 'T' and 't' attributes are, or the 'S' and 's' or even the 'r', 'w', and 'x' since this is all just random stuff.
Like I said, BTDT.
What I did was went in with a low level binary editor and cleared out the inodes. Difficult and hairy stuff. I think there are other tools now, over and above fsck.
That is, backup and format again the disk. I see no other way. Or ignore the files, as they seem to be small. Meaning that fsck is broken itself, too. :-/ -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 07/12/2014 08:31 PM, Carlos E. R. wrote:
Meaning that fsck is broken itself, too. :-/
Not broken: inadequate. See things like http://lde.sourceforge.net/lde_man.txt You need to use something like http://linux.about.com/library/cmd/blcmdl8_debugfs.htm to zap the inode and then use fsck to clean up the blocks that don't seems to be allocated to any inode ... That is the ones that might have been or might not have been to the zapped inode. Thinks: if the corrupted node appears to point its 'file' to blocks that actually belong to another file, then fsck will see them as belonging to that other file. See also http://serverfault.com/questions/315700/how-to-determine-which-file-inode-oc... which can lead to some interesting details of 'under the hood' -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-07-13 02:39, Anton Aylward wrote:
On 07/12/2014 08:31 PM, Carlos E. R. wrote:
Meaning that fsck is broken itself, too. :-/
Not broken: inadequate.
After all, neither :-) We had forgotten about the attributes, not permissions, of the files. I never use them myself... -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2014-07-13 03:04 (GMT+0200) Carlos E. R. composed:
We had forgotten about the attributes, not permissions, of the files. I never use them myself...
I do rather often lately, e.g.: https://bugzilla.novell.com/show_bug.cgi?id=887039 and for /boot/message, which I change to have the Tux theme used 100% of the time, and every gfxboot update tries to change back to the ugly default. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-07-13 03:20, Felix Miata wrote:
On 2014-07-13 03:04 (GMT+0200) Carlos E. R. composed:
We had forgotten about the attributes, not permissions, of the files. I never use them myself...
I do rather often lately, e.g.: https://bugzilla.novell.com/show_bug.cgi?id=887039
Oh.
and for /boot/message, which I change to have the Tux theme used 100% of the time, and every gfxboot update tries to change back to the ugly default.
I have, on occasion, used cronjob to undo those things. It is less intrusive or disrupting, for those things like you found in your bug report, and it does the job - albeit with delay. Otherwise, I could write a script to run after any install job, to set up all those things I forget. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2014-07-13 02:31, Carlos E. R. wrote:
On 2014-07-13 02:13, Anton Aylward wrote:
What you have is corrupted inodes. The 'ls' command is trying its best to interpret the random bit patterns of the inodes. Its mapping the random junk there into what *you* interpret as various status bit according to the manual page. But really they are just nonsense. That is why you cannot delete anything. It's all corrupt.
That /does/make sense.
I'm getting progress. Telcontar:/mnt/Ext/Moria2/lost+found # chattr = \#4047692 Telcontar:/mnt/Ext/Moria2/lost+found # l \#4047692 ---xr-S--t 1 2195736830 1610809728 36864 May 24 1985 #4047692* Telcontar:/mnt/Ext/Moria2/lost+found # rm \#4047692 Telcontar:/mnt/Ext/Moria2/lost+found # l \#4047692 ls: cannot access #4047692: No such file or directory Telcontar:/mnt/Ext/Moria2/lost+found # Telcontar:/mnt/Ext/Moria2/lost+found # lsattr \#* --SDi-d-c---T--- #4049402 --S-ia--c---T--- #4066597 ---Di---cj-tT--- #4079810 -----adAcj--T--- #4083190 Telcontar:/mnt/Ext/Moria2/lost+found # chattr = \#* Telcontar:/mnt/Ext/Moria2/lost+found # lsattr \#* ---------------- #4049402 ---------------- #4066597 ---------j------ #4079810 ---------j------ #4083190 Telcontar:/mnt/Ext/Moria2/lost+found # Telcontar:/mnt/Ext/Moria2/lost+found # l total 268 drw-rw---T 2 2225140482 1073897600 40960 Jul 13 02:50 #4048177/ d-wxrw-r-x 2 113311111 3129454 45056 Aug 18 1969 #4049358/ ---sr----T 1 821969126 1091361282 49152 May 22 1990 #4049402* drwxr-s--T 2 2166404463 2700568576 45056 May 13 1970 #4065600/ ---x--x-w- 1 79724563 239075460 40960 Dec 26 1974 #4066597* ---Sr---wt 1 1497693200 4013616054 45056 Feb 9 1902 #4079810* --w-rwxr-x 1 3529138678 2276790368 49152 Feb 18 1971 #4083190* dr--r-s--T 2 858947044 857867178 36864 Sep 10 1948 #4083819/ drwxr-xr-x 6 root root 20480 Jul 13 02:49 ./ drwxr-xr-x 11 root root 4096 Aug 4 2012 ../ Telcontar:/mnt/Ext/Moria2/lost+found # Telcontar:/mnt/Ext/Moria2/lost+found # rmdir \#4048177/ Telcontar:/mnt/Ext/Moria2/lost+found # rmdir \#4049358/ Telcontar:/mnt/Ext/Moria2/lost+found # rmdir \#4065600/ Telcontar:/mnt/Ext/Moria2/lost+found # rmdir \#4083819/ Telcontar:/mnt/Ext/Moria2/lost+found # rm \#4049402 \#4066597 \#4079810 \#4083190 Telcontar:/mnt/Ext/Moria2/lost+found # l total 24 drwxr-xr-x 2 root root 20480 Jul 13 02:53 ./ drwxr-xr-x 11 root root 4096 Aug 4 2012 ../ Telcontar:/mnt/Ext/Moria2/lost+found # GOTCHA! :-)) I got the hint here: http://forums.cpanel.net/f5/cannot-delete-file-root-164270.html post number 4 asks to use lsattr. I found the rest myself. :-) I see later in the thread they say "chattr -i" worked. That apparently refers to "immutable" bit. Only some of my files had it. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I have a Linux based multimedia box (not openSUSE), to which I connect via telnet. It has an external hard disk via usb, formatted as ext2 (2, not 3 nor 4). It runs kernel 2.4.21-xfs, and BusyBox v1.01 (2006.11.30-16:43+0000).
As the disk is connected via usb, I can, when not in use, connect it to my openSUSE machine. I use that sometimes for maintenance of the disk.
Other times, I use the fsck facility on the machine itself. After one of these runs, I found some files on the lost+found directory; I copied them to my openSUSE machine via ftp, for later inspection, then attempted to delete them on the machine. FTP (with 'mc') deleted most, but not all.
Looking via telnet, I see very strange permissions:
[root@Moria:/usb/lost+found]# ls -l - ---xr-S--t 1 -2099230 16108097 36864 May 24 1985 #4047692 drw-rw---T 2 -2069826 10738976 40960 Jul 11 2036 #4048177 d-wxrw-r-x 2 11331111 3129454 45056 Aug 18 1969 #4049358 - ---sr----T 1 82196912 10913612 49152 May 22 1990 #4049402 drwxr-s--T 2 -2128562 -1594398 45056 May 13 1970 #4065600 - ---x--x-w- 1 79724563 23907546 40960 Dec 26 1974 #4066597 - ---Sr---wt 1 14976932 -2813512 45056 Feb 9 1902 #4079810 - --w-rwxr-x 1 -7658286 -2018176 49152 Feb 18 1971 #4083190 dr--r-s--T 2 85894704 85786717 36864 Sep 10 1948 #4083819 [root@Moria:/usb/lost+found]# rmdir \#4065600/ rmdir: `#4065600/': Operation not permitted [root@Moria:/usb/lost+found]#
I'm not familiar with those permissions. But I can not delete them. I can not change the permissions either:
[root@Moria:/usb/lost+found]# rmdir \#4065600/ rmdir: `#4065600/': Operation not permitted [root@Moria:/usb/lost+found]# chmod u+r+w \#4065600/ chmod: #4065600/: Operation not permitted [root@Moria:/usb/lost+found]# chown root \#4065600/ chown: #4065600/: Operation not permitted [root@Moria:/usb/lost+found]#
The current permissions are:
drwxr-s--T 2 -2128562 -1594398 45056 May 13 1970 #4065600
How can I delete those files?
What means the 'T' and 't' attributes?
t = sticky bit. On a directory, it means that any user with write permission can create a file in the directory, but write permission on the directory is restricted in that you can't remove a file owned by another user. s = setuid bit Change user ID to that of the file owner -- only has an effect on binary executables g = setgid bit Change group ID to that of file's group -- only has an effect on binary executables. Often used for game high score files.
Ideas?
Check to see if the filesystem is mounted read-only.
Of course, I'll try, when the device is not needed, to connect the disk to openSUSE and try from here, to see if things are different :-?
- -- Cheers
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlPBqEsACgkQtTMYHG2NR9X/fQCfTclCwuYIb4IoGKYxePUF00OZ OiwAoI0qyHBMj+cPPLar7TXsDPiUgKXa =vxWe -----END PGP SIGNATURE-----
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (9)
-
Anton Aylward -
Carlos E. R. -
David C. Rankin -
Dirk Gently -
Felix Miata -
Freek de Kruijf -
jdd -
John Andersen -
Ken Schneider - openSUSE