From: Tim Dijkstra <newsuser@famdijkstra.org>
To: Luis Rodrigo Gallardo Cruz <rodrigo@nul-unu.com>, 415441@bugs.debian.org
Cc: Neil Brown <neilb@suse.de>,
suspend-devel List <suspend-devel@lists.sourceforge.net>,
Michael Tokarev <mjt@tls.msk.ru>,
linux-raid@vger.kernel.org
Subject: Re: Bug#415441: s2disk and raid
Date: Tue, 17 Apr 2007 20:58:18 +0200 [thread overview]
Message-ID: <20070417205818.22fd2d9d@commensaal.drs.p> (raw)
In-Reply-To: <20070412053753.GA3602@lisa.rodrigo.nul-unu.com>
[-- Attachment #1.1: Type: text/plain, Size: 1540 bytes --]
On Thu, 12 Apr 2007 00:37:53 -0500
Luis Rodrigo Gallardo Cruz <rodrigo@nul-unu.com> wrote:
> On Thu, Apr 05, 2007 at 12:47:49AM +0400, Michael Tokarev wrote:
> > Neil Brown wrote:
> > > On Tuesday April 3, newsuser@famdijkstra.org wrote:
> > []
> > >> After the power cycle the kernel boots, devices are discovered, among
> > >> which the ones holding raid. Then we try to find the device that holds
> > >> swap in case of resume and / in case of a normal boot.
> > >>
> > >> Now comes a crucial point. The script that finds the raid array, finds
> > >> the array in an unclean state and starts syncing.
> > []
> > > So you can start arrays 'readonly', and resume off a raid1 without any
> > > risk of the the resync starting when it shouldn't.
> >
> Something that I seem to not have said. It's not *all* arrays that are
> unclean on reboot, just one (that is used as physical volume for
> LVM. I don't know if that's relevant). Also worth mentioning is that
> kernel space suspend on 2.6.17 did not have this problem (or didn't
> show it in my system, anyways).
>
> After reading through the responses, I have come to think this is a
> kernel issue, and have posted a report (#418823) to debian's linux-2.6
> package. I'll wait to see what they have to say.
Maybe there is a kernel issue, but we still are doing something wrong;
We shouldn't try to write to raid before we resume, that is just asking
for problems.
I'll look into the `readonly' option. That would fix or problem IMHO.
grts Tim
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 286 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
[-- Attachment #3: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Suspend-devel mailing list
Suspend-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/suspend-devel
next prev parent reply other threads:[~2007-04-17 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 15:55 s2disk and raid Tim Dijkstra
2007-04-03 16:34 ` [Suspend-devel] " Stefan Seyfried
2007-04-03 19:00 ` Rafael J. Wysocki
2007-04-04 5:20 ` Neil Brown
2007-04-04 18:53 ` Tim Dijkstra
2007-04-04 20:47 ` Michael Tokarev
2007-04-12 5:37 ` Luis Rodrigo Gallardo Cruz
2007-04-17 18:58 ` Tim Dijkstra [this message]
2007-04-06 9:08 ` Luca Berra
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=20070417205818.22fd2d9d@commensaal.drs.p \
--to=newsuser@famdijkstra.org \
--cc=415441@bugs.debian.org \
--cc=linux-raid@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=neilb@suse.de \
--cc=rodrigo@nul-unu.com \
--cc=suspend-devel@lists.sourceforge.net \
/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).