From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Laurent CARON <lcaron@apartia.fr>
Cc: reiserfs-list@namesys.com
Subject: Re: ReiserFS 3.6 - Unable to access some files
Date: Tue, 20 Dec 2005 18:29:01 +0300 [thread overview]
Message-ID: <43A8233D.3090603@namesys.com> (raw)
In-Reply-To: <43A82161.6090706@apartia.fr>
Hello
Laurent CARON wrote:
> Vladimir V. Saveliev a écrit :
>
>> Hello
>>
>> Laurent CARON wrote:
>>
>>
>>> Hi,
>>>
>>> I'm currently using a big (1.2Tb) Reiser3.6 filesystem under debian SID
>>> (Kernel 2.6.13).
>>>
>>> Problem: I'm trying to delete a file, but unfortunately.... it won't me
>>> delete it.
>>>
>>> server:/var/tmp# rm -Rf network.old
>>> rm: cannot remove `network.old/Makefile': Permission denied
>>>
>>>
>>
>> is there anything in system logs?
>>
>>
> No error in the logs.
>
>>
>>
>>> cd ./network.old
>>> server:/var/tmp/network.old# ls -al
>>> ls: Makefile: Permission denied
>>> total 0
>>> drwxrwxrwt+ 2 root Domain Users 72 2005-07-13 10:17 ./
>>> drwxrwxrwt 4 root root 104 2005-12-02 13:42 ../
>>>
>>> server:/var/tmp/network.old# stat *
>>> stat: cannot stat `Makefile': Permission denied
>>>
>>>
>>> Is this a filesystem corruption, a bug in reiserfs....?
>>>
>>>
>>
>> It looks like a filesystem corruption: there is a name in a directory,
>> but the
>> file itself can not be found.
>>
>>
> If it is a "little" FS corruption, a reiserfsck --fix-fixable
> /dev/partition should "normally" be able to fix it .?.?
>
yes, reiserfsck --fix-fixable will fix it if there is nothing worse.
So, you should start with "reiserfsck /dev/partition" and see what it says.
prev parent reply other threads:[~2005-12-20 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 15:09 ReiserFS 3.6 - Unable to access some files Laurent CARON
2005-12-20 15:15 ` Vladimir V. Saveliev
2005-12-20 15:21 ` Laurent CARON
2005-12-20 15:29 ` Vladimir V. Saveliev [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43A8233D.3090603@namesys.com \
--to=vs@namesys.com \
--cc=lcaron@apartia.fr \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.