On Thu, 12 Apr 2007 00:37:53 -0500 Luis Rodrigo Gallardo Cruz <rodrigo@xxxxxxxxxxx> wrote: > On Thu, Apr 05, 2007 at 12:47:49AM +0400, Michael Tokarev wrote: > > Neil Brown wrote: > > > On Tuesday April 3, newsuser@xxxxxxxxxxxxxxx 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:
signature.asc
Description: PGP signature
