On Monday 02 July 2007 00:12:14 Neil Brown wrote:
Kernel logs from the boot would help here.
Logs would help.
Sure. The interesting part from dmesg is this:
hdg: max request size: 512KiB
hdg: 398297088 sectors (203928 MB) w/8192KiB Cache, CHS=24792/255/63,
UDMA(100)
hdg: cache flushes
David Greaves wrote:
Tejun Heo wrote:
It's really weird tho. The PHY RDY status changed events are coming
from the device which is NOT used while resuming
There is an obvious problem there though Tejun (the errors even when sda
isn't involved in the OS boot) - can I start another thread
On Monday, 2 July 2007 12:56, Tejun Heo wrote:
David Greaves wrote:
Tejun Heo wrote:
It's really weird tho. The PHY RDY status changed events are coming
from the device which is NOT used while resuming
There is an obvious problem there though Tejun (the errors even when sda
isn't
On Monday, 2 July 2007 16:32, David Greaves wrote:
Rafael J. Wysocki wrote:
On Monday, 2 July 2007 12:56, Tejun Heo wrote:
David Greaves wrote:
Tejun Heo wrote:
It's really weird tho. The PHY RDY status changed events are coming
from the device which is NOT used while resuming
There
On Monday, 2 July 2007 18:36, David Greaves wrote:
Rafael J. Wysocki wrote:
On Monday, 2 July 2007 16:32, David Greaves wrote:
Rafael J. Wysocki wrote:
On Monday, 2 July 2007 12:56, Tejun Heo wrote:
David Greaves wrote:
Tejun Heo wrote:
It's really weird tho. The PHY RDY status
Hello Justin ( all) ,
On Thu, 28 Jun 2007, Justin Piszcz wrote:
On Thu, 28 Jun 2007, Peter Rabbitson wrote:
Justin Piszcz wrote:
On Thu, 28 Jun 2007, Peter Rabbitson wrote:
Interesting, I came up with the same results (1M chunk being superior)
with a completely different raid set
