Hi,
I have a strange problem. when i do ls i see a folder, say 'abc', but it disappears when i do ls -l. I cannot access or mv that folder. Solaris 10 (SPARC) doesn't allow me to create a new folder with the same name, as it already exists.
'file' command also doesn't recognize i 'abc' existance.
yazu
September 6, 2011, 9:30am
2
NFS? If not check the file system if you can.
its local disk. i can't run an fsck on it right now. du -sh * shows it as an empty folder (0k)
pludi
September 6, 2011, 10:14am
4
What's the output of ls -lba
? Any funny \-escapes?
nope, any use of -l, and 'ban_output' is not listed.
[root@server] # ls
ban_output disableusers.txt process.txt user_20100601_102804.xml.log
cal.txt disableusers.txt_20110904 sctssb.txt user_20110104_121943.xml.log
calendar_bak_old dse.ldif.bak stscripts wipeluminis
config.txt dse.ldif.startOK tmp working
configman.lst media user_20100523_113801.xml.log
dead.letter migration user_20100531_113208.xml.log
disable_users_20100713 plumcrt01.conf user_20100601_081926.xml.log
[root@server] # ls -l
total 24288
-rw-r--r-- 1 root root 11457237 Jun 6 2010 cal.txt
drwx------ 2 root root 512 Apr 13 2010 calendar_bak_old
-rw-r--r-- 1 root root 244072 Dec 11 2010 config.txt
-rw-r--r-- 1 root root 230512 Apr 28 2010 configman.lst
-rw------- 1 root root 931 Apr 12 2010 dead.letter
-rw-r--r-- 1 root root 241 Jul 13 2010 disable_users_20100713
-rw-r--r-- 1 root root 627 Sep 4 13:43 disableusers.txt
-rw-r--r-- 1 root root 427 Jul 3 10:51 disableusers.txt_20110904
-rw------- 1 root root 185245 Nov 25 2010 dse.ldif.bak
-rw------- 1 root root 185245 Nov 25 2010 dse.ldif.startOK
drwxr-xr-x 2 root root 512 Apr 13 2010 media
drwxr-xr-x 5 root root 512 Apr 18 2010 migration
-rw-r--r-- 1 root root 1240 Apr 12 2010 plumcrt01.conf
-rw-r--r-- 1 root root 8685 Apr 28 2010 process.txt
-rw-r--r-- 1 root root 169 Apr 14 2010 sctssb.txt
drwxr-xr-x 2 root root 512 Apr 14 2010 stscripts
drwxr-xr-x 2 root root 29184 Sep 5 11:12 tmp
-rw-r--r-- 1 root root 326 May 23 2010 user_20100523_113801.xml.log
-rw-r--r-- 1 root root 326 May 31 2010 user_20100531_113208.xml.log
-rw-r--r-- 1 root root 326 Jun 1 2010 user_20100601_081926.xml.log
-rw-r--r-- 1 root root 326 Jun 1 2010 user_20100601_102804.xml.log
-rw-r--r-- 1 root root 326 Jan 4 2011 user_20110104_121943.xml.log
-rwxr-xr-x 1 root root 16453 Apr 12 2010 wipeluminis
drwxr-xr-x 3 root root 512 Apr 14 2010 working
Tommyk
September 6, 2011, 11:35am
6
try an "ls -i" to get the inode number?
That works.
67115 ban_output
but can i access it using inode. I can't find it using the inum option in the find command
Tommyk
September 6, 2011, 11:43am
8
find ./ -inum 67115 -exec ls -ial {} \;
try that to see if you can find the information based on its inode. if it does show anything try changing the ls command for a cat command or vi command depending on what you want to do with it.
no luck, finding using inode doesn't work. du works too. I just want to remove the directory and create a new one. I don't think it contains any data.
[root@server] # find ./ -inum 67115 -exec ls -ial {} \;
find: stat() error ./ban_output: No such file or directory
[root@server] # find ./ -inum 67115 -exec cat {} \;
find: stat() error ./ban_output: No such file or directory
[root@server] # find ./ -inum 67115 -exec vi {} \;
find: stat() error ./ban_output: No such file or directory
[root@server] # du -sh * | grep -i ban
0K ban_output
[root@server] # rmdir ban_output
rmdir: directory "ban_ouput": Directory does not exist
df -h -> what does the following mean:
df: cannot statvfs /export/home/lumadmin/ban_output: No such file or directory
pludi
September 6, 2011, 3:35pm
10
That probably means that the directory name contains a special character, which is why I asked you to post the output of ls -lba
. The b
is an additional option to show these specials, which makes it a whole lot easier to clear the problem!
Tried
ls -lba
but with no luck. I doubt it uses a special character, because i cannot
mkdir ban_output
---------- Post updated at 09:16 AM ---------- Previous update was at 02:43 AM ----------
Fixed. sorry, it turns out the folder was an NFS mount point after all. :o
Just restarted the NFS client and it worked.
Thank You guys for all your time and effort.