From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Armando Di Cianno <fafhrd@gentoo.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: Test patch for sleep on Aluminium PowerBooks
Date: Tue, 23 Nov 2004 09:20:53 +1100 [thread overview]
Message-ID: <1101162053.13597.136.camel@gaston> (raw)
In-Reply-To: <fc01eab7ddb069d0da7030a94b467f8f@nephilim.localdomain>
> Does this patch do, or should have to do, anything special to
> "normalize" the mounted filesystems before sleep? When I patched the
> kernel first, I was running XFS, and of course that is notorious for
> file corruptions with power abnormalities on a system. I started to
> get really odd file corruptions, where 'ls file' would should the
> file, but 'ls -l file' would not.
I though xfs was supposed to be journaled ? Yes, the sleep code will
sync all disks before sleep. You should update to patch #4 though, there
have been number of problems fixes since then.
> I switched to ReiserFS (v3) now, and have seen symptoms like this
> problem caused appear once more (but not to the extent that XFS showed
> [where I thought my system was disintegrating before my eyes]).
Hrm... reiserfs is evil, ask any sane kernel hacker :) Why not ext3 ?
> Is there something that was overlooked in the patch, or something that
> I'm overlooking that needs to be done?
>
> If filesystems do not need to be "normalized" at sleep, what
> filesystems are known to work? (Hesistant about ext3, as it's quite
> slow, imho, but I'll go that route if needed, I suppose).
It's not that slow ...
Ben.
next prev parent reply other threads:[~2004-11-22 22:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 9:50 Test patch for sleep on Aluminium PowerBooks Benjamin Herrenschmidt
2004-10-27 17:50 ` David Woodhouse
2004-11-09 3:11 ` Armando Di Cianno
2004-11-22 22:20 ` Benjamin Herrenschmidt [this message]
2004-11-22 22:26 ` Colin Leroy
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=1101162053.13597.136.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=fafhrd@gentoo.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).