Hi!
> >Stop spreading fud. Take powersave + suspend from
> >suse10.2, and see
> >if you can break it.
> >
> >sata_nv seems to have problem, that's it. and it
> >triggered problem in
> >reiserfs. Use ext3 if you care about your data, and yes
> >your drivers
> >need to support suspend/resume.
>
Hi!
Stop spreading fud. Take powersave + suspend from
suse10.2, and see
if you can break it.
sata_nv seems to have problem, that's it. and it
triggered problem in
reiserfs. Use ext3 if you care about your data, and yes
your drivers
need to support suspend/resume.
My Compaq
Pavel Machek wrote:
On Tue 12-12-06 23:45:27, Olivier Galibert wrote:
On Tue, Dec 12, 2006 at 11:44:18AM -0700, Andrew Robinson wrote:
When I said hibernate, I did mention it was to disk, not to ram.
Suspend to disk is not trustable on Linux, and does not look like it
will be
On Tue 12-12-06 23:45:27, Olivier Galibert wrote:
> On Tue, Dec 12, 2006 at 11:44:18AM -0700, Andrew Robinson wrote:
> > When I said hibernate, I did mention it was to disk, not to ram.
>
> Suspend to disk is not trustable on Linux, and does not look like it
> will be any time soon. Suspend to
On Tue 12-12-06 23:45:27, Olivier Galibert wrote:
On Tue, Dec 12, 2006 at 11:44:18AM -0700, Andrew Robinson wrote:
When I said hibernate, I did mention it was to disk, not to ram.
Suspend to disk is not trustable on Linux, and does not look like it
will be any time soon. Suspend to ram has
Pavel Machek wrote:
On Tue 12-12-06 23:45:27, Olivier Galibert wrote:
On Tue, Dec 12, 2006 at 11:44:18AM -0700, Andrew Robinson wrote:
When I said hibernate, I did mention it was to disk, not to ram.
Suspend to disk is not trustable on Linux, and does not look like it
will be
Andrew Robinson wrote:
When I said hibernate, I did mention it was to disk, not to ram. I
woke my computer up from work remotely using wakeonlan. When the
computer was responsive, I started getting I/O errors and when I saw
my kernel log I saw file corruption problems with my "/dev/sda2"
device
Andrew Robinson wrote:
When I said hibernate, I did mention it was to disk, not to ram. I
woke my computer up from work remotely using wakeonlan. When the
computer was responsive, I started getting I/O errors and when I saw
my kernel log I saw file corruption problems with my /dev/sda2
device
On Tue, Dec 12, 2006 at 11:44:18AM -0700, Andrew Robinson wrote:
> When I said hibernate, I did mention it was to disk, not to ram.
Suspend to disk is not trustable on Linux, and does not look like it
will be any time soon. Suspend to ram has a better chance of becoming
reliable, but at that
Phillip Susi wrote:
If your comment here was in reply to my general comment about resierfs
stability and not the specific hibernation issue the OP was having,
please edit the quote down to just that portion instead of quoting the
entire message, including the quotes it was replying to.
I
No. I still see corruption on Suse with Reiser FS. It's always very
subtle (like the last block of a file doesn;t get copied or gets
corrupted. We have been running our ftp server on ReiserFS, and as
soon as I can get it moved back to ext3, we are doing so.
We have had a lot of issues with
Phillip Susi wrote:
Andrew Robinson wrote:
Now I am confused on what may be the cause of the corruption. Could it
have been just a ReiserFS problem (I will be using Ext3 or JSF on my
next rebuild I think after reading some reviews on the ReiserFS and
this recent experience).
I have been
Andrew Robinson wrote:
Now I am confused on what may be the cause of the corruption. Could it
have been just a ReiserFS problem (I will be using Ext3 or JSF on my
next rebuild I think after reading some reviews on the ReiserFS and
this recent experience).
I have been running reiser on my home
Okay, I'm having a really bad day (or week) and I want to apologize
for the rantish email. I just went back into the configuration for the
new kernel, and I was wrong about the experimental state of the SATA,
but it appears the PATA state is experimental instead.
Now I am confused on what may be
Okay, I'm having a really bad day (or week) and I want to apologize
for the rantish email. I just went back into the configuration for the
new kernel, and I was wrong about the experimental state of the SATA,
but it appears the PATA state is experimental instead.
Now I am confused on what may be
Andrew Robinson wrote:
Now I am confused on what may be the cause of the corruption. Could it
have been just a ReiserFS problem (I will be using Ext3 or JSF on my
next rebuild I think after reading some reviews on the ReiserFS and
this recent experience).
I have been running reiser on my home
Phillip Susi wrote:
Andrew Robinson wrote:
Now I am confused on what may be the cause of the corruption. Could it
have been just a ReiserFS problem (I will be using Ext3 or JSF on my
next rebuild I think after reading some reviews on the ReiserFS and
this recent experience).
I have been
No. I still see corruption on Suse with Reiser FS. It's always very
subtle (like the last block of a file doesn;t get copied or gets
corrupted. We have been running our ftp server on ReiserFS, and as
soon as I can get it moved back to ext3, we are doing so.
We have had a lot of issues with
Phillip Susi wrote:
If your comment here was in reply to my general comment about resierfs
stability and not the specific hibernation issue the OP was having,
please edit the quote down to just that portion instead of quoting the
entire message, including the quotes it was replying to.
I
On Tue, Dec 12, 2006 at 11:44:18AM -0700, Andrew Robinson wrote:
When I said hibernate, I did mention it was to disk, not to ram.
Suspend to disk is not trustable on Linux, and does not look like it
will be any time soon. Suspend to ram has a better chance of becoming
reliable, but at that
20 matches
Mail list logo
