3 July 2012
(using FreeBSD 8.2 with ZFS raidz1 over 4 drives)
I was dd'ing from /dev/zero to a file on the raid. Before the dd'ing finished, I
unwittingly initiated a cp from that file to another file on the raid. A little while
later, the entire system seemed to "freeze". (i.e., all log activities, crontabs, mail
services, ssh, network, etc. stopped). When I rebooted the system, I discovered that the
second file had the time stamp around the "freeze" time. However, the first file dd
had completed (the expected size was correct) and had a timestamp that was well
after the "freeze" time.
So, it looked like the system partially kernel panic'd but finished the dd.
How would I find out what happened? My system is headless, therefore I don't have console.
There doesn't seem to be any kernel dumps or any logged activity after the "freeze" time.
(I checked messages, auth.log, and maillog so far) Anywhere else?
-phil
(using FreeBSD 8.2 with ZFS raidz1 over 4 drives)
I was dd'ing from /dev/zero to a file on the raid. Before the dd'ing finished, I
unwittingly initiated a cp from that file to another file on the raid. A little while
later, the entire system seemed to "freeze". (i.e., all log activities, crontabs, mail
services, ssh, network, etc. stopped). When I rebooted the system, I discovered that the
second file had the time stamp around the "freeze" time. However, the first file dd
had completed (the expected size was correct) and had a timestamp that was well
after the "freeze" time.
So, it looked like the system partially kernel panic'd but finished the dd.
How would I find out what happened? My system is headless, therefore I don't have console.
There doesn't seem to be any kernel dumps or any logged activity after the "freeze" time.
(I checked messages, auth.log, and maillog so far) Anywhere else?
-phil