-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday, 2014-07-04 at 11:40 +1000, Dave Chinner wrote:
On Fri, Jul 04, 2014 at 03:29:31AM +0200, Carlos E. R. wrote:
No, it is not. Root is separate and using ext4. The problematic one
is /home.
What I did, as far I remember, was, when I noticed that home had
failed and was read only, to switch to runlevel 1, umount /home
(killing the apps that were still using it), then tried to mount it
again to replay the log, prior to using xfs-repair on it. Mount
hung. ctrl-alt-supr failed, or appeared to fail. So reset button...
That's a completely different issue to having a shutdown filesystem
hang your system. That's a mount problem, and likely a known issue.
You need to be specific when describing a problem, otherwise we
waste time going down the wrong paths.
Sorry for the misunderstanding.
But halt/reboot did hung, even if it was after a failed mount. I was
trying to recover the system, remember, and I'm trying to remember what
exactly I did do, from memory, not written records.
No, the on disk filesystem is not healthy. If I continue using it,
after reboot and using "xfs_repair" several times, it fails again
within a day.
After at least one hibernation and thaw cycle, right?
Yes. 3, I think.
Then hibernation has caused the corruption. It may take some time
for the corruption to be detected, but there isn't any doubt in my
mind that hibernation is the cause of your problems.
Wait.
The sequence was:
healthy system
several hibernation cycles.
failure on come back from hibernation, with kernel error: XFS_WANT_CORRUPTED_GOTO.
reboot - kernel error messages: XFS_WANT_CORRUPTED_RETURN, which I probably did not see.
repair filesytem
several hibernation cycles during some hours.
failure on come back from hibernation, with kernel error: XFS_WANT_CORRUPTED_GOTO
See that there were kernel error messages right after rebooting, which I
think I did not see at the time, because had I seen them I would have
rebooted again, and I did not.
- From the log, already posted:
<0.5> 2014-03-15 03:49:42 Telcontar kernel - - - [ 19.173599] XFS (sdd5): Mounting Filesystem
<0.5> 2014-03-15 03:49:42 Telcontar kernel - - - [ 19.377918] XFS (sdd5): Starting recovery (logdev: internal)
<0.5> 2014-03-15 03:49:42 Telcontar kernel - - - [ 19.747914] XFS (sdd5): Ending recovery (logdev: internal)
<3.6> 2014-03-15 03:53:01 Telcontar systemd 4987 - - Starting Default.
<3.6> 2014-03-15 03:53:01 Telcontar systemd 4987 - - Reached target Default.
<3.6> 2014-03-15 03:53:01 Telcontar systemd 4987 - - Startup finished in 57ms.
<3.6> 2014-03-15 03:53:01 Telcontar systemd 1 - - Started User Manager for 9.
<0.1> 2014-03-15 03:53:47 Telcontar kernel - - - [ 301.857523] XFS: Internal error XFS_WANT_CORRUPTED_RETURN at line 350 of file /home/abuild/rpmbuild/BUILD/kernel-desktop-3.11.10/linux-3.11/fs/xfs/xfs_all
Then I think I run xfs-repair, which did not complain, and I continued
working. Within the day, after 3 hibernations, it failed again with
XFS_WANT_CORRUPTED_GOTO, and I decided I had to reboot, backup, reformat,
restore.
So, until we have kernel fixes, you'd do best to turn off
hibernation. If you can't live with leaving your machine powered up
or switching it off, then use suspend-to-ram rather than
suspend-to-disk to avoid the problematic snapshot/restore
situation....
Impossible... this is a desktop, not a laptop. Suspend to ram is high
risk, even if it works (which I think it doesn't).
If the failure is unavoidable, I'll reformat the partition as ext4
instead... which I do not like, but such is life.
But before that, I'll try upgrade xfsprogs.
- --
Cheers,
Carlos E. R.
(from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlO2FKQACgkQtTMYHG2NR9USxgCeOdJeJORl2JpnsnhqtXDj2ZCL
3IIAniMFd9X+ETWr3gVPHYq7SFwIPKSt
=WPe7
-----END PGP SIGNATURE-----
_______________________________________________
xfs mailing list
xfs@xxxxxxxxxxx
http://oss.sgi.com/mailman/listinfo/xfs
