All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miguel <turtle.power@wanadoo.es>
To: Alexy Khrabrov <list+reiserfs@setup.org>
Cc: ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: immutability
Date: Sun, 30 May 2004 20:16:16 +0200	[thread overview]
Message-ID: <20040530201616.5ba654ba.turtle.power@wanadoo.es> (raw)
In-Reply-To: <20040529152153.GA20663%alexy.khrabrov@setup.org>

On Sat, 29 May 2004 11:21:54 -0400
Alexy Khrabrov <list+reiserfs@setup.org> 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.

Yes but backup is a bit annoyning when you need to recover just a few
files, I'm using a procedure on my machines to restore recently deleted
files (24h).

Firt you need libtrash (http://www.m-arriaga.net/software/libtrash/)
which intercepts some system calls when you try to delete a file and mv
those files to a special directory.

Then tmpreaper cleans the "trash" directory deleting old files when
atime > 24h in my case.

(http://packages.debian.org/unstable/admin/tmpreaper)

it's easy and 100% userspace.


> 
> So, just to confirm -- is there chattr or a similar way to make files
> immutable?  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?
> 
> -- 
> Cheers,
> Alexy Khrabrov :: www.setup.org :: Age Quod Agis
> 


-- 
La resistencia es fútil todos seréis asimilados

  reply	other threads:[~2004-05-30 18:16 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 ` Miguel [this message]
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 ` immutability Vladimir Saveliev

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=20040530201616.5ba654ba.turtle.power@wanadoo.es \
    --to=turtle.power@wanadoo.es \
    --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.