Public bug reported:
I have an amd64 machine with Edgy. There are filve disks in. One ATA
(hda) and four SATA (sda, sdb, sdc, sdd). All the four SATA disks are
composed into an RAID5 array.
The suspend part seems to be good. But the resume have problem. There is
the log from resume. I have an idea but no time for test it. So when I
makes my computer to suspend to disk the RAID array does not syncing
before power off. When the computer starting again the md detects the
raid array dirty and going to reconstructing it. AFTER the raid started
the initrd detects the suspend signature on swap device and wants to
stop tasks. It can't stop the md_resync and aborts resume and going over
normal startup.
Jan 6 17:22:03 homepc kernel: [ 36.027295] raid5: automatically using best
checksumming function: generic_sse
Jan 6 17:22:03 homepc kernel: [ 36.058822] generic_sse: 6156.000 MB/sec
Jan 6 17:22:03 homepc kernel: [ 36.070594] raid5: using function:
generic_sse (6156.000 MB/sec)
Jan 6 17:22:03 homepc kernel: [ 36.085382] md: md driver 0.90.3
MAX_MD_DEVS=256, MD_SB_DISKS=27
Jan 6 17:22:03 homepc kernel: [ 36.097360] md: bitmap version 4.39
Jan 6 17:22:03 homepc kernel: [ 36.110941] md: raid5 personality registered
for level 5
Jan 6 17:22:03 homepc kernel: [ 36.123108] md: raid4 personality registered
for level 4
Jan 6 17:22:03 homepc kernel: [ 36.425154] md: md0 stopped.
Jan 6 17:22:03 homepc kernel: [ 36.439052] md: bind<sdb>
Jan 6 17:22:03 homepc kernel: [ 36.451273] md: bind<sdc>
Jan 6 17:22:03 homepc kernel: [ 36.463425] md: bind<sdd>
Jan 6 17:22:03 homepc kernel: [ 36.475483] md: bind<sda>
Jan 6 17:22:03 homepc kernel: [ 36.487404] md: md0: raid array is not clean
-- starting background reconstruction
Jan 6 17:22:03 homepc kernel: [ 36.504617] raid5: device sda operational as
raid disk 0
Jan 6 17:22:03 homepc kernel: [ 36.517003] raid5: device sdd operational as
raid disk 3
Jan 6 17:22:03 homepc kernel: [ 36.529279] raid5: device sdc operational as
raid disk 2
Jan 6 17:22:03 homepc kernel: [ 36.541430] raid5: device sdb operational as
raid disk 1
Jan 6 17:22:03 homepc kernel: [ 36.553742] raid5: allocated 4262kB for md0
Jan 6 17:22:03 homepc kernel: [ 36.565645] raid5: raid level 5 set md0
active with 4 out of 4 devices, algorithm 0
Jan 6 17:22:03 homepc kernel: [ 36.577765] RAID5 conf printout:
Jan 6 17:22:03 homepc kernel: [ 36.589771] --- rd:4 wd:4 fd:0
Jan 6 17:22:03 homepc kernel: [ 36.601615] disk 0, o:1, dev:sda
Jan 6 17:22:03 homepc kernel: [ 36.613514] disk 1, o:1, dev:sdb
Jan 6 17:22:03 homepc kernel: [ 36.625183] disk 2, o:1, dev:sdc
Jan 6 17:22:03 homepc kernel: [ 36.636698] disk 3, o:1, dev:sdd
Jan 6 17:22:03 homepc kernel: [ 36.648231] ieee1394: Host added:
ID:BUS[0-00:1023] GUID[00148556003b9181]
Jan 6 17:22:03 homepc kernel: [ 36.654699] md: syncing RAID array md0
Jan 6 17:22:03 homepc kernel: [ 36.666075] md: minimum _guaranteed_
reconstruction speed: 1000 KB/sec/disc.
Jan 6 17:22:03 homepc kernel: [ 36.677535] md: using maximum available idle
IO bandwidth (but not more than 200000 KB/sec) for reconstruction.
Jan 6 17:22:03 homepc kernel: [ 36.689207] md: using 128k window, over a
total of 244198464 blocks.
Jan 6 17:22:03 homepc kernel: [ 48.358304] Freezing cpus ...
Jan 6 17:22:03 homepc kernel: [ 48.358308] Stopping tasks: ==========
Jan 6 17:22:03 homepc kernel: [ 68.344801] stopping tasks timed out after
20 seconds (1 tasks remaining):
Jan 6 17:22:03 homepc kernel: [ 68.344805] md0_resync
Jan 6 17:22:03 homepc kernel: [ 68.344807] Restarting tasks...<6> Strange,
md0_resync not stopped
Jan 6 17:22:03 homepc kernel: [ 68.347740] done
Jan 6 17:22:03 homepc kernel: [ 68.347741] Thawing cpus ...
Jan 6 17:22:03 homepc kernel: [ 68.492491] Attempting manual resume
Jan 6 17:22:03 homepc kernel: [ 68.587480] EXT3-fs: INFO: recovery required
on readonly filesystem.
Jan 6 17:22:03 homepc kernel: [ 68.599756] EXT3-fs: write access will be
enabled during recovery.
Jan 6 17:22:03 homepc kernel: [ 74.490328] kjournald starting. Commit
interval 5 seconds
Jan 6 17:22:03 homepc kernel: [ 74.502476] EXT3-fs: recovery complete.
Jan 6 17:22:03 homepc kernel: [ 74.517237] EXT3-fs: mounted filesystem with
ordered data mode.
** Affects: Ubuntu
Importance: Undecided
Status: Unconfirmed
--
swsusp fails to resume
https://launchpad.net/bugs/78223
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs