On Sun, 2003-01-26 at 18:38, Greg Lehey wrote:
Did you use shutdown -p? If my hypothesis is correct, it's possible
to get this result with shutdown -h if you press the power switch as
soon as the System halted message appears, but normally you'd give
it a few seconds longer. With shutdown
On Sun, Jan 26, 2003 at 04:08:31PM +0800, Greg Lehey wrote:
On Sunday, 26 January 2003 at 14:24:02 +1030, Daniel O'Connor wrote:
On Sun, 2003-01-26 at 08:08, David Schultz wrote:
Good. I was referring to IDE in this case, because I assume
that's what Greg's laptop uses. The ATA driver
Thus spake Greg Lehey [EMAIL PROTECTED]:
I've been thinking about what happened, and I have a possibility: the
session before shutdown included a lot of writing to that file system,
and I did a shutdown -p. It's possible that the shutdown powered off
the system before the disk had flushed
David Schultz wrote:
I still can't figure out why the problem would trash your entire
home directory, though. Even if the disk reordered writes and
failed to write some sectors, directory entries that were not
being actively modified shouldn't have become corrupted, as far as
I
On Sunday, 26 January 2003 at 14:24:02 +1030, Daniel O'Connor wrote:
On Sun, 2003-01-26 at 08:08, David Schultz wrote:
Good. I was referring to IDE in this case, because I assume
that's what Greg's laptop uses. The ATA driver flushes the cache
when the device is closed, but I don't think
On Fri, Jan 24, 2003 at 11:03:52PM -0800, David Schultz wrote:
FreeBSD's ``fix'' for this problem is the same as Windows 98's.
Specifically, there is a 5-second delay (tuneable:
kern.shutdown.poweroff_delay) after all buffers are flushed but
before the power is cut. Maybe we ought to be
On Fri, 24 Jan 2003, David Schultz wrote:
Thus spake Greg Lehey [EMAIL PROTECTED]:
I've been thinking about what happened, and I have a possibility: the
session before shutdown included a lot of writing to that file system,
and I did a shutdown -p. It's possible that the shutdown powered
Thus spake Nate Lawson [EMAIL PROTECTED]:
On Fri, 24 Jan 2003, David Schultz wrote:
Thus spake Greg Lehey [EMAIL PROTECTED]:
I've been thinking about what happened, and I have a possibility: the
session before shutdown included a lot of writing to that file system,
and I did a shutdown
On Sun, 2003-01-26 at 08:08, David Schultz wrote:
Good. I was referring to IDE in this case, because I assume
that's what Greg's laptop uses. The ATA driver flushes the cache
when the device is closed, but I don't think that happens during
shutdown. It probably needs to register a shutdown
I'm rather astounded. I'm currently at a Linux conference, and have
of course been boasting about the stability of ufs, and today I had a
crash which tore apart my /home file system.
This is on a laptop, one which has been running -CURRENT for years
with no trouble. At the moment it's running
Greg Lehey [EMAIL PROTECTED] wrote:
It has
three file systems, one of which came up dirty. fsck -y reported
thousands of errors, and when it was finished, my home directory and
some other files were gone, and all the subdirectories of my home
directory were in lost+found, a total of 1.4 GB.
Next time you run fsck -y in this scenario, log the output to an md
partition and stick it somewhere for analysis. At least, that was the
moral of the story last time I hosed a box in this form (incidentally, I
think it ended up being a failing hard disk).
Robert N M Watson FreeBSD
three file systems, one of which came up dirty. fsck -y reported
thousands of errors, and when it was finished, my home directory and
some other files were gone, and all the subdirectories of my home
This may (or may not) have anything to do with it, but I had a problem with
a couple of
On Friday, 24 January 2003 at 20:34:24 +1000, Andy Farkas wrote:
I'm rather astounded. I'm currently at a Linux conference, and have
of course been boasting about the stability of ufs, and today I had a
crash which tore apart my /home file system.
This is on a laptop, one which has been
Thus spake Greg Lehey [EMAIL PROTECTED]:
I've been thinking about what happened, and I have a possibility: the
session before shutdown included a lot of writing to that file system,
and I did a shutdown -p. It's possible that the shutdown powered off
the system before the disk had flushed its
15 matches
Mail list logo
