This is a good one - lets see if anyone can figure it out
FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
[root@mickeyboy mickey]# cd ???Eb????o%?0??}?? w???M??n??????uz???@?,A????3???????eI?B?OOf;s?{E???X?U <?l?????@59?????
bash: cd: ???Eb????o%?0??}??: No such file or directory
bash: ?l?????@59?????: No such file or directory
It's driving me nuts , sitting there on my user home directory and no matter what
command i use to remove it I can't remove it.
And how it got there was a accident , it isn't affecting anything.
Please help before I go over the deep end.
If I don't get rid of it pretty soon I'm going back to $Windows.
If I don't get rid of it pretty soon I'm going back to $Windows.
That's pretty lame.
Anyway, as root user ( su - ) I created the said directory and removed it like this......
Code:
# mkdir "???Eb????o%?0??}?? w???M??n??????uz???@?,A????3???????eI?B?OOf;s?{E???X?U <?l?????@59?????"
# ls
Desktop
???Eb????o%?0??}?? w???M??n??????uz???@?,A????3???????eI?B?OOf;s?{E???X?U <?l?????@59?????
Then, I used the command: rm -rf ??? and pressed the tab key to complete the directory name. It came out looking like this....
# rm -rf \?\?\?Eb\?\?\?\?o%\?0\?\?\}\?\?\ w\?\?\?M\?\?n\?\?\?\?\?\?uz\?\?\?\@\?\,A\?\?\?\?3\?\?\?\?\?\?\?eI\?B\?OOf\;s\?\{E\?\?\?X\?U\ \<\?l\?\?\?\?\?\@59\?\?\?\?\?/
Now the ls comfirms that it is gone.
# ls
Desktop
#
And what's really wierd is that if you look at the directory with Super User file manager it shows that Root doesn't even have permission to read it.
It has a lock in front of it .
Even after you have issued the command and put the first ? and then <tab> it won't even list out the complete directory name, like ? isn't
the first character of the directory name , which inicates that it is..
Maybe you will have some luck using find .
For example, I change to the user directory and run this command to see how old the directory is.
In this case -mtime -1 is looking for directories that are less than one day old.
Code:
# find . -maxdepth 1 -type d -mtime -1 -exec ls -d {} \;
.
./test2
./test
./test1
Once I know how old the directory is, I can use find again to remove it.....
Code:
# find . -maxdepth 1 -type d -mtime -1 -exec rm -rf {} \;
Then I run the first find to verify that the new directories are gone.
# find . -maxdepth 1 -type d -mtime -1 -exec ls -d {} \;
.
#
I'm not sure why this hasn't been suggested, but usually when I find a directory like that I have some sort of file system corruption. Login as root (preferably under single user mode or from a boot disk) and do a thorough scan with 'fsck' ('man fsck' for help).
(I updated this considering macemoneta's comments)
Under Fedora Core, you would want init level 1 (single user, no services started). Init level 3 is defined in Fedora as multi-user mode, all services started, without X. Running fsck in that mode will cause file system corruption, if you don't already have it. Be careful with init levels; different distributions define them differently.
Not that I'm recommending, but just thought I would point out that I've done full fsck scans on runlevel 3 with multiple services and have never had file corruption. But I guess the best thing is to do whatever the instructions say.
The problem is that fsck is directly modifying on-disk data, while the kernel filesystem has a different view. In single-user mode, only root is running, and root is only executing fsck, so the two views can't get out of sync. In multi-user mode, various applications are writing (logs, for example), so fsck updates a data structure, then the kernel flushes buffers with a sync, and now there's a fine mess. Timing, and which data structures are being updated, matter of course so there's no guarantee that there will be damage; it's just a very unsafe situation.
Well guys , we will have to carry on another day with this little project, I just crashed my Linux box
because of the improper use of FSCK. Another day.
Read Post "I crashed my FC3 PC, need help with Knoppix"
Thanks for your help.
Jim
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.