From: Marcus Wanner <marcusw@cox.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Compressed Filesystem
Date: Wed, 30 Dec 2009 09:12:29 -0500 [thread overview]
Message-ID: <4B3B5FCD.8000502@cox.net> (raw)
In-Reply-To: <1262132249.136326.8.camel@centar>
On 12/29/2009 7:17 PM, Albert Hopkins wrote:
> On Wed, 2009-12-30 at 00:08 +0100, Volker Armin Hemmann wrote:
>
>> just think a moment of the tons of bug fixes constantly going into
>> ext4. That
>> crap is not stable. Pre-alpha maybe.
>>
> People say this from time to time, yet I have been running ext4 on my
> root directory of my laptop since July 2008. The only problem I've had
> since then is one time it would not mount on boot. I merely had to fsck
> it from a live media an then it was ok (nothing lost or currupted). But
> that was a long time ago when it was still ext4dev. And I've had
> numerous crashes and battery depletions on the laptop without incident.
> So the pre-alpha FUD that some people are spreading is either not true
> or I just happen to be the luckiest ext4 user in the world :-).
>
For my two cents, a while back I was on ext4 and was trying to get xorg
working. My problem was that the input drivers were not working (because
they had not been recompiled after an update), so once I ran startx, no
keyboard or mouse input was registered. This meant that every time I
tried something which I thought would fix it, I had to hard reset the
system and look at the logs. The only problem was that the logs had the
wrong contents because they had been "written to" but not actually
flushed to the disk, and it took me about 10 hard resets to figure that
out. Even though I was running ext4, I never lost a thing (except the
logs :p).
For the curious, I eventually got good logs by running shutdown -h 1 in
one tty right before running startx in the other, and that shutdown the
system correctly.
Marcus
next prev parent reply other threads:[~2009-12-30 14:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
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=4B3B5FCD.8000502@cox.net \
--to=marcusw@cox.net \
--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