From: Dave Chinner <david@fromorbit.com>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: xfs@oss.sgi.com
Subject: Re: truncated files
Date: Thu, 27 Nov 2008 09:59:31 +1100 [thread overview]
Message-ID: <20081126225931.GK6291@disturbed> (raw)
In-Reply-To: <200811260949.19642.Martin@lichtvoll.de>
On Wed, Nov 26, 2008 at 09:49:18AM +0100, Martin Steigerwald wrote:
> Am Dienstag 25 November 2008 schrieb Dave Chinner:
> > On Tue, Nov 25, 2008 at 10:44:14PM +0100, Martin Steigerwald wrote:
> > > Hi!
> > >
> > > Today on one try to hibernate via tuxonice it machine appeared dead.
> > > I am
> >
> > ^^^^^^^^^
> > When (not if) suspend to disk/resume fails, you get to keep all the
> > broken pieces of your filesystem. It works most of the time, but it has
> > some fundamentally broken corner cases that you probably just
> > hit....
>
> Well I use TuxOnIce for a reason! I had uptimes of up to 70 days with it
> already. And they are usually only interrupted by kernel updates or
> manual shutdowns. I was never convinced by in-kernel solutions for
> hibernate.
Sure, though I'm not convinced that TuxOnIce is any better because
it still uses the same fundamental design as the in-kernel ones.
> > I've never had a system that suspends reliably (let alone resumes
> > from the suspend) so it's no real surprise that I don't trust
> > suspend to disk....
>
> Well I take it as bad luck then, especially since there are no hints that
> XFS had a problem. I am not sure whether the machine really was dead, but
> I can't reproduce what exactly happened. So thats it.
And therein lies the problem. I can't get suspend/resume to work
reliably on anything I own, so I can't do anything about problems
reported as a result of suspend/resume. Hell, I even considered
running linux on my new laptop inside a virtual machine on windows
just so I could have functioning suspend/resume....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2008-11-26 23:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 21:44 truncated files Martin Steigerwald
2008-11-25 22:27 ` Dave Chinner
2008-11-26 8:49 ` Martin Steigerwald
2008-11-26 22:59 ` Dave Chinner [this message]
2008-11-28 22:02 ` Martin Steigerwald
2008-11-28 22:39 ` Martin Steigerwald
2008-11-29 7:24 ` hangs with MTRR_SANITIZER? (was: Re: truncated files) Martin Steigerwald
2008-11-29 7:24 ` Martin Steigerwald
2008-11-29 23:02 ` hangs with MTRR_SANITIZER? - no, something else Martin Steigerwald
2008-11-29 23:02 ` Martin Steigerwald
2008-12-08 8:40 ` [TuxOnIce-devel] hangs with MTRR_SANITIZER? - solved Martin Steigerwald
2008-12-08 8:40 ` Martin Steigerwald
-- strict thread matches above, loose matches on Subject: below --
2008-11-25 22:03 truncated files Martin Steigerwald
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=20081126225931.GK6291@disturbed \
--to=david@fromorbit.com \
--cc=Martin@lichtvoll.de \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.