Date: Thu, 28 Jun 2001 20:14:24 -0700 From: "Brigg Angus" <brigg@flatlan.net> To: <freebsd-questions@FreeBSD.org> Subject: Re: somewhat interesting rm issue Message-ID: <003a01c10049$99b0d4c0$02000a0a@desertflora.com> References: <01Jun28.130929pdt.119046@gatekeeper.bcrail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for the reply, as I hadn't thought of that and useful for future problems. It would have been unlikely for spaces to exist in the file name since I renamed the file (was extra special careful) and the chmod command worked without too much misgivings. There were no error messages associated with the rm or rm-rf commands. As it turns out, the solution was easy (maybe even obvious). I simply rebooted the Windows machine and was then able to rm the file. What weird perfidious SMB parameter held its evil grip on this file to such an extent as to prevent deletion is beyond my understanding, but that probably rests in the purview of Samba. Thanks, Brigg > What error messages are you getting? Maybe the name contains some spaces. > Try rm -i blah* > > Chris > > -----Original Message----- > From: Brigg Angus [mailto:brigg@flatlan.net] > Sent: Thursday, June 28, 2001 1:07 PM > To: freebsd-questions@FreeBSD.org > Subject: somewhat interesting rm issue > > > I'm wondering if there's a way to rm a file that cannot be deleted by any of > the regular methods. For instance, I had copied the contents of the Win98 SE > reskit over from the Win98 CD to my home directory via Windows98/Samba. In > trying to remove the reskit directory, one file, .nmH7Kghj could not be > removed. I can successfully change the name (changed too "blah"), I can > change the contents (file had an original size of 0 bytes), "chmod 777 blah" > works fine (although there have been issues with it automatically reverting > to chmod 655 here and there, with no reason I can divine), "unlink blah" > does not work, "rm -rf blah" does not work, "chflags nouunlnk blah" does not > work. When I rm or rm -rf the file there is no error message, but the file > remains. > > "ls -ol blah" has yielded both, > -rw-r-xr-x 1 777 brigg - 13 Jun 27 21:31 blah > -rwxrwxrwx 1 777 brigg - 13 Jun 27 21:31 blah > > Running 4.3-stable > > Any ideas on what may be causing this, or a solution, would be appreciated. > Brigg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003a01c10049$99b0d4c0$02000a0a>