What to do with a damaged directory?

opensuse 13.1
linux 3.11.10-25-desktop x86_64

Somehow a directory used as a mount point has become damaged.

Various attempts (as root) to correct the problem:

$ ls /
[other dirs removed]
d?????????   ? ?          ?           ?            ? t2/
$ mv t2 t2-bkp
mv: cannot stat ‘t2’: Permission denied
$ rmdir t2
rmdir: failed to remove ‘t2’: Device or resource busy

How do I fix this?

On Thu, 08 Jan 2015 20:36:01 +0000, jimoe666 wrote:

> opensuse 13.1 linux 3.11.10-25-desktop x86_64
>
> Somehow a directory used as a mount point has become damaged.
>
> Various attempts (as root) to correct the problem:
>
> Code:
> --------------------
> $ ls /
> [other dirs removed]
> d??? ? ? ? ? ? t2/ $ mv t2
> t2-bkp mv: cannot stat ‘t2’: Permission denied $ rmdir t2 rmdir:
> failed to remove ‘t2’: Device or resource busy
> --------------------
>
> How do I fix this?

I actually ran into something similar to this a few days ago - I was
using a fuse filesystem mounted on the directory that I had to kill
because of a recursive directory problem, and ended up with a similar
output.

First thing I’d look for is the output of ‘mount’. See if the ‘t2’ entry
is listed in the list of mounted filesystems.

If it is, start by removing that. In my case, I did that and the
directory reverted to a normal entry that I was then able to remove using
normal commands.

If that doesn’t work, you may need to boot into recovery and run a
filesystem check (fsck) on the root partition.

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

On 2015-01-08 21:36, jimoe666 wrote:
>
> opensuse 13.1
> linux 3.11.10-25-desktop x86_64
>
> Somehow a directory used as a mount point has become damaged.

with nothing mounted there this moment?

I think you have to fsck the root filesystem, using a rescue system; the
installation disk has a minimal one, but I prefer using the oS 13.1 XFCE
rescue image.

If, on the other hand, whatever should mount there is mounted is still
mounted when you have the issue, then you have to umount it and fsck it.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

Ah. That jogged a brain cell. One thing I did not try was to un-mount the volume. That cleared the mess with scrambled flags and such. I could then mount the volume. Back in business. Thanks!

On Thu, 08 Jan 2015 22:56:01 +0000, jimoe666 wrote:

> hendersj;2688033 Wrote:
>> On Thu, 08 Jan 2015 20:36:01 +0000, jimoe666 wrote:
>> First thing I’d look for is the output of ‘mount’. See if the ‘t2’
>> entry is listed in the list of mounted filesystems.
> Ah. That jogged a brain cell. One thing I did not try was to un-mount
> the volume. That cleared the mess with scrambled flags and such. I could
> then mount the volume. Back in business. Thanks!

Glad to hear that worked. :slight_smile:

Jim


Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C