1833779 Members
1955 Online
110063 Solutions
New Discussion

File sdlogs

 
Samuel Alfonzo
Occasional Contributor

File sdlogs

Hi,
I have a file in the directory / , It's called sdlogs and It has the folowing permissions:

lrwxrwxrwx 1 root root 20 Nov 1 12:07 sdlogs

I tried eliminate it, with : rm, rm -f, rm -Rf, unlink; but I don't have success, because It's returning me Device Busy.

Can you help me with this?????
Thanks

Finding the truth
6 REPLIES 6
John Poff
Honored Contributor

Re: File sdlogs

Hi,

The 'l' in the first position indicates that you are looking at a symlink. Probably the file that it is symlinked to is held open by another process. Try 'fuser sdlogs' and you can see the processes that are holding it open, and then you can do 'ps -fp ' for them to see what they are.

What does a full 'ls -l sdlogs' look like? That should show you the symlink.

JP
Robin Wakefield
Honored Contributor

Re: File sdlogs

Hi,

I would guess this is a symlink someone/something has created to the Software Distributor log area. Can you show what the link is pointing to?

Rgds, Robin
Samuel Alfonzo
Occasional Contributor

Re: File sdlogs

I tried to do 'fuser sdlogs' and It returned me
'sdlogs: stat: Permission denied
fuser: could not find or access file sdlogs'

It's very estrange, because the symbol link don't appear.

Regards
Finding the truth
John Poff
Honored Contributor

Re: File sdlogs

Are you running the 'fuser' command as root?

JP
Samuel Alfonzo
Occasional Contributor

Re: File sdlogs

yeah, all the command was executed with root.
Finding the truth
John Poff
Honored Contributor

Re: File sdlogs

You could try an 'ls -li sdlogs' and get the inode number for that file. Then, try 'find / -xdev -inum ####' where the #### is the inode number from the 'ls -li' command. Since the stat command failed during the 'fuser' command, I suspect that the inode for this file may be hosed up.

It might be time for an 'fsck' on the / filesystem, which is pretty tough to do when the system is running. You could reboot the system and get the 'fsck' on / for free. Some of the other real wizards here might have a better idea for getting the filesystem checked. I hate doing reboots just to fix strange problems, but this might be one of those problems where it is justified.

JP