public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bill Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] compressed filesystem
Date: Thu, 01 Sep 2011 16:01:20 +0800	[thread overview]
Message-ID: <1314864080.529.36.camel@troll> (raw)
In-Reply-To: <CAC=wYCEOSz5zPFuVxwm3G0XsLe45aapW0rHnyeZ39PsG5HJBUw@mail.gmail.com>

2.6.37 on one machine, and 2.6.39 on the other - those two corrupted
during bad shutdowns whilst writing to the FS (well, I am bad for
triggering the remote power OFF :)

Its not the corruption that was the issue, but that a wipe, reformat and
reload was the only fix.  Cant remember the exact error - its been known
for awhile, but wasn't all that common  when i searched for it.

If they get a set of usable tools, especially online fsck I'd go back to
it as having a drive offline for hours whilst checking reiserfs isn't
great (though at least it doesnt happen often)

BillK



On Thu, 2011-09-01 at 17:13 +1000, Adam Carter wrote:
> > Is it reliable?
> 
> So far so go for me. I'm using lzo on my main partition and zlib on
> /home and on an external drive i use for backup.
> 
> > A month ago I returned all my BTRFS partitions to reiserfs because of
> > unfixable errors.  Initially I was quite impressed,  but until the tools
> > catch up with real world problems I'll watch from the sidelines.  Errors
> > will happen, but fixing them is important too.
> 
> Which kernel was that with? Was the issue caused by a power loss or
> normal running? The lack of tools is why Fedora are sticking with ext4
> for 16.
> 





  reply	other threads:[~2011-09-01  8:02 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31 15:50 [gentoo-user] compressed filesystem Space Cake
2011-08-31 16:21 ` Nilesh Govindarajan
2011-08-31 16:23   ` Nilesh Govindarajan
2011-08-31 23:37   ` Adam Carter
2011-09-01  7:04     ` Bill Kenworthy
2011-09-01  7:13       ` Adam Carter
2011-09-01  8:01         ` Bill Kenworthy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-12-28 11:58 [gentoo-user] Compressed Filesystem Helmut Jarausch
2009-12-28 12:10 ` Mike Kazantsev
2009-12-28 12:29 ` William Kenworthy
2009-12-28 18:44 ` Volker Armin Hemmann
2009-12-29  8:31   ` Helmut Jarausch
2009-12-29 13:04     ` Volker Armin Hemmann
2009-12-29 23:01       ` Stefan G. Weichinger
2009-12-29 23:08         ` Volker Armin Hemmann
2009-12-30  0:17           ` Albert Hopkins
2009-12-30  0:45             ` Volker Armin Hemmann
2009-12-30 13:48             ` Stroller
2009-12-30 14:12             ` Marcus Wanner
2009-12-30 14:20               ` Volker Armin Hemmann
2009-12-31  1:04               ` Neil Bothwick
2009-12-31  2:57                 ` Marcus Wanner
2009-12-31  4:18                   ` Dale
2009-12-31  8:20                     ` Volker Armin Hemmann
2009-12-31 16:54                       ` Marcus Wanner
2009-12-31 17:20                       ` Dale
2009-12-30  9:20           ` Stefan G. Weichinger
2010-01-03  6:35 ` Enrico Weigelt
2010-01-03 11:53   ` Helmut Jarausch
2010-01-03 13:48     ` Mike Kazantsev
2010-02-06  0:03     ` Enrico Weigelt

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=1314864080.529.36.camel@troll \
    --to=billk@iinet.net.au \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox