From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Jason A. Lixfeld" <jlixfeld@fastvibe.com>
Cc: 'Theodore Tso' <tytso@mit.edu>,
ext3-users@redhat.com, linux-lvm@sistina.com
Subject: [linux-lvm] Re: What really works?
Date: Tue Oct 23 05:35:02 2001 [thread overview]
Message-ID: <20011023113614.B2334@redhat.com> (raw)
In-Reply-To: <001101c15b68$5adbb880$836788cf@industry>; from jlixfeld@fastvibe.com on Mon, Oct 22, 2001 at 10:13:48PM -0400
Hi,
On Mon, Oct 22, 2001 at 10:13:48PM -0400, Jason A. Lixfeld wrote:
> This is still a very annoying problem. chattr -i <-- I corrected it
> this time :) Doesn't make the files or directories deletable. Any
> other ideas?
Use "chattr -ia". The "-a" (append-only) attribute will also pin the
files against deletion.
Failing that, "debugfs" lets you forcibly delete files: "clri
<filename>" will clear the inode by force, and a subsequent e2fsck
will fix up the fs summary information to be consistent with the
destroyed file (including deleting the directory entry pointing to the
nuked inode).
Cheers,
Stephen
next prev parent reply other threads:[~2001-10-23 5:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E15vISM-0005YX-00.2001-10-21-14-15-58@mail5.svr.pol.co.uk>
2001-10-21 14:25 ` [linux-lvm] What really works? Jason A. Lixfeld
2001-10-22 14:37 ` [linux-lvm] " Theodore Tso
2001-10-22 14:42 ` Bryan-TheBS-Smith
2001-10-22 21:13 ` [linux-lvm] " Jason A. Lixfeld
2001-10-23 5:35 ` Stephen C. Tweedie [this message]
2001-10-22 17:04 ` [linux-lvm] " Stephen C. Tweedie
2001-10-22 17:22 ` Andreas Dilger
2001-10-23 5:32 ` Stephen C. Tweedie
2001-10-23 4:42 ` Joe Thornber
2001-11-02 9:40 ` Stephen C. Tweedie
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=20011023113614.B2334@redhat.com \
--to=sct@redhat.com \
--cc=ext3-users@redhat.com \
--cc=jlixfeld@fastvibe.com \
--cc=linux-lvm@sistina.com \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).