On Wed, Jul 30, 2008 at 12:34 AM, Zhu Sha Zang <[EMAIL PROTECTED]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Andrey Falko escreveu: > | On Tue, Jul 29, 2008 at 11:49 PM, Zhu Sha Zang <[EMAIL PROTECTED]> > wrote: > | Hi everybody, > | > | I have some disaster in my desktop system because i'm erased my /lib. > | Well, i've solved this problem unpacking stage-3 over my system, and > emerge > | -e world. > | My system working very well now, but a weak problem appear. > | > | In boot, when tmpdir tried to be cleaned, some messages appear that the > some > | directories don't be erased., this: > | > | drwxrwxrwx 2 root 1003 4.0K Jul 13 08:24 ashura > | drwxrwxrwx 2 505 101 4.0K Jul 15 11:41 dasusr1 > | drwxrwxrwx 2 507 102 4.0K Jul 15 11:41 db2inst1 > | drwxrwx--T 7 root rodolfo 4.0K Jul 30 03:34 rodolfo > | drwx-----T 2 root root 4.0K Jul 30 00:06 root > | > | I've tried to remove this directories usimg root after boot, and receive > | this message: > | > | sakurazukamori .private # rm -rf * > | rm: cannot remove directory `ashura': Operation not permitted > | rm: cannot remove directory `dasusr1': Operation not permitted > | rm: cannot remove directory `db2inst1': Operation not permitted > | rm: cannot remove directory `rodolfo': Operation not permitted > | rm: cannot remove directory `root': Operation not permitted > | > | Thinking in some service using this directories, i've tried boot a gentoo > | livecd and erase archies but the same problem appear. > | I used too fsck on this ext3 file system, none errors on fylesystem are > | detected. > | > | Some tricks? > | thnks for now > |> > |> > |> > |> > |> > |> > _______________________________________________________ Yahoo! Mail - Sempre > a melhor opção para você! Experimente já e veja as novidades. > http://br.yahoo.com/mailbeta/tudonovo/ > |> > |> > > | You might have extended attributes enabled. What happens when you run > | lsattr on that directory? If you don't have lsattr, emerge e2fsprogs. > > Using lsattr -Ra in /tmp: > > sakurazukamori tmp # lsattr -Ra > - ----------I--- ./. > - -------------- ./.. > - -------------- ./.X0-lock > - -------------- ./.ICE-unix > > ./.ICE-unix: > lsattr: Operation not supported While reading flags on > ./.ICE-unix/dcop4790-1217369151 > - ----------I--- ./.ICE-unix/.. > - -------------- ./.ICE-unix/. > > - -----a-------- ./.private > > ./.private: > - -------------- ./.private/ashura > > ./.private/ashura: > - -----a-------- ./.private/ashura/.. > - -------------- ./.private/ashura/. > > - -------------- ./.private/db2inst1 > > ./.private/db2inst1: > - -----a-------- ./.private/db2inst1/.. > - -------------- ./.private/db2inst1/. > > - -------------- ./.private/rodolfo > > ./.private/rodolfo: > - -----a-------- ./.private/rodolfo/.. > - -------------- ./.private/rodolfo/. > > - ----------I--- ./.private/.. > - -------------- ./.private/dasusr1 > > ./.private/dasusr1: > - -----a-------- ./.private/dasusr1/.. > - -------------- ./.private/dasusr1/. > > - -----a-------- ./.private/. > - -------------- ./.private/root > > ./.private/root: > - -----a-------- ./.private/root/.. > - -------------- ./.private/root/. > > > - -------------- ./gpg-j3M7SQ > > ./gpg-j3M7SQ: > lsattr: Operation not supported While reading flags on > ./gpg-j3M7SQ/S.gpg-agent > - ----------I--- ./gpg-j3M7SQ/.. > - -------------- ./gpg-j3M7SQ/. > > - -------------- ./.X11-unix > > ./.X11-unix: > lsattr: Operation not supported While reading flags on ./.X11-unix/X0 > - ----------I--- ./.X11-unix/.. > - -------------- ./.X11-unix/. > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkiQGZ8ACgkQbLyL8mxGP9S2KgCgrPxc21Mu0zo1YRbwz7Hedm/i > FtsAoLnsn8jBJDv0Ui8CXlfDwVrP1N2F > =RTbE > -----END PGP SIGNATURE----- > >
As I suspected, you have some extended attributes set. Do you know how this could have happen? You willl have to unset them. How I don't know. When this happen to me with JFS, I trashed the filesystem and never looked back. This however is happening to ext3!, so I am very surprised.
