Rafael J. Wysocki wrote:
On Saturday, 16 June 2007 21:56, David Greaves wrote:
This isn't a regression.
I was seeing these problems on 2.6.21 (but 22 was in -rc so I waited to try it).
I tried 2.6.22-rc4 (with Tejun's patches) to see if it had improved - no.
Note this is a different (desktop) machine to that involved my recent bugs.
The machine will work for days (continually powered up) without a problem and
then exhibits a filesystem failure within minutes of a resume.
I know xfs/raid are OK with hibernate. Is lvm?
The root filesystem is xfs on raid1 and that doesn't seem to have any problems.
What is the partition that's showing problems? How's it set up, on how many
I did put that in the OP :)
Here's a recap...
/dev/mapper/video_vg-video_lv on /scratch type xfs (rw)
md1 : active raid5 sdd1 sda1 sdc1
390716672 blocks level 5, 64k chunk, algorithm 2 [3/3] [UUU]
--- Physical volume ---
PV Name /dev/md1
VG Name video_vg
PV Size 372.62 GB / not usable 3.25 MB
Allocatable yes (but full)
PE Size (KByte) 4096
Total PE 95389
Free PE 0
Allocated PE 95389
PV UUID IUig5k-460l-sMZc-23Iz-MMFl-Cfh9-XuBMiq
Also, is the dmesg output below from right after the resume?
It runs OK for a few minutes - just enough to think "hey, maybe it'll work this
time". Not more than an hour of normal use.
Then you notice when some app fails because the filesystem went away.
The dmesg comes from that point.