All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zan Lynx <zlynx@acm.org>
To: Mat <jackdachef@gmail.com>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Reiser4: errors AFTER fsck
Date: Mon, 07 Apr 2008 10:16:46 -0600	[thread overview]
Message-ID: <1207585006.31700.2.camel@localhost> (raw)
In-Reply-To: <loom.20080405T115310-647@post.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 929 bytes --]

On Sat, 2008-04-05 at 12:06 +0000, Mat wrote:
> Volker,
> 
> storing the portage-tree on a "critical" partition such as /var isn't probably a
> good idea (yet), 
> reiser4 gets more stable on an almost daily / weekly basis now but I still have
> the feeling that it's somewhat fragile in terms of use as a / (root / system)
> partition; data-partitions seem to be completely rock-solid & safe, though :)

I have been using Reiser4 as / on my laptop for a couple of years now
and have not had any serious problems that caused data loss.  I've had a
few problems here and there but they have been solved fairly quickly.
I've had to run full tree rebuilds overnight several times but never
lost anything I've missed. :)

I do run nightly backups to an external disk, that's probably why I
never lost anything.  Murphy is waiting for the external disk to fail
before he screws me. :)
-- 
Zan Lynx <zlynx@acm.org>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-04-07 16:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-05 12:06 Reiser4: errors AFTER fsck Mat
2008-04-07 16:16 ` Zan Lynx [this message]
2011-02-08 19:02   ` Dushan Tcholich
  -- strict thread matches above, loose matches on Subject: below --
2008-04-04 17:38 Volker Armin Hemmann
2008-04-04 20:21 ` Edward Shishkin
2008-04-04 20:50   ` Volker Armin Hemmann
2008-04-04 20:54   ` Volker Armin Hemmann
2008-04-05  9:38     ` Edward Shishkin
2008-04-05  9:46       ` Volker Armin Hemmann
2008-04-05 19:16         ` Volker Armin Hemmann

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=1207585006.31700.2.camel@localhost \
    --to=zlynx@acm.org \
    --cc=jackdachef@gmail.com \
    --cc=reiserfs-devel@vger.kernel.org \
    /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.