From: Vladimir Saveliev <vs@namesys.com>
To: Alexy Khrabrov <list+reiserfs@setup.org>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: immutability
Date: Mon, 31 May 2004 11:40:39 +0400 [thread overview]
Message-ID: <1085989239.1198.44.camel@tribesman.namesys.com> (raw)
In-Reply-To: <20040529152153.GA20663%alexy.khrabrov@setup.org>
Hello
On Sat, 2004-05-29 at 19:21, Alexy Khrabrov wrote:
> About immutability...
>
> Now I have to confess, I've deleted those two files while trying to
> make them immutable whith chattr. I didn't realize it applies to
> ext2/3 filesystems, and lsattr did show ..-i-... Seeing i, I did rm,
> and there they went. On the good side, I know what to do now if I
> accidentally delete a file on Linux, which is no small feat -- for years,
> I just thought, forget it. Unix approach to recovery was, and still is,
> "backup", and if you didn't, you're an idiot whose files are not worth
> recovery anyway. :) Undoing an rm on Linux is a deeply vindicating
> experience :). I wonder what v4 offers in that area. And even with
> the current routine, as can be easily seen, there could be automated
> assembly scripts.
>
> So, just to confirm -- is there chattr or a similar way to make files
> immutable?
reiserfs has mount option attrs (mount -o attrs). chattr and lsattr
starts to work then. You may have to run reiserfsck --clean-attributes
before using it, though
> I use a RAID to store digital photographs, running LVM on
> top of it consisting of the RAID physical volume only, and reiserfs in
> the logical volume spanning the only volume group spanning the RAID.
> The idea was, I'll just get those logical extents I need in case I
> need a used part of it -- here I'd need help from reiserfs's bitmap,
> still have to figure that out, that's what my original "partial dd"
> question was about. I'd like to make the files "write once" via some
> kind of automated process. Is there any way simpler than remounting
> the thing read-only after each write from a CF card?
prev parent reply other threads:[~2004-05-31 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 15:21 immutability Alexy Khrabrov
2004-05-30 18:16 ` immutability Miguel
2004-06-05 14:31 ` immutability Sander
2004-06-05 14:57 ` immutability Miguel
2004-05-30 19:13 ` immutability mjt
2004-05-31 7:40 ` Vladimir 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=1085989239.1198.44.camel@tribesman.namesys.com \
--to=vs@namesys.com \
--cc=list+reiserfs@setup.org \
--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.