raid1 narrow_write_error with 4K disks, sd "bad block number requested" messages

2015-01-29 Thread Nate Dailey
l, version 3.10.0-221.el7. I took a look at upstream sd and md changes and nothing jumps out at me that would have affected this (but I have not tested to see if the bad block messages do or do not happen on an upstream kernel). I'd appreciate any advice re: how to handle this. Thanks! Nat

Re: raid1 narrow_write_error with 4K disks, sd "bad block number requested" messages

2015-02-12 Thread Nate Dailey
On 02/04/2015 11:59 PM, NeilBrown wrote: On Wed, 28 Jan 2015 10:29:46 -0500 Nate Dailey wrote: I'm writing about something that appears to be an issue with raid1's narrow_write_error, particular to non-512-byte-sector disks. Here's what I'm doing: - 2 disk raid1, 4K disk

[PATCH] drivers/scsi/sr_ioctl.c: check for failed allocation

2005-04-21 Thread Nate Dailey
Hi, I noticed a case in sr_ioctl.c's sr_get_mcn where a buffer is allocated, but the pointer isn't checked for null. This patch against 2.6.12-rc2 adds a check. Nate Dailey Stratus Technologies Signed-off-by: Nate Dailey <[EMAIL PROTECTED]> --- linux-2.6.12-rc2/drivers/scsi

[PATCH] drivers/scsi/st.c: decrement in_use under the lock in st_open

2005-04-21 Thread Nate Dailey
ing in_use in other places. This is against kernel 2.6.12-rc2. Nate Dailey Stratus Technologies Signed-off-by: Nate Dailey <[EMAIL PROTECTED]> --- linux-2.6.12-rc2/drivers/scsi/st.c.orig 2005-04-20 11:28:39.0 -0400 +++ linux-2.6.12-rc2/drivers/scsi/st.c 2005-04-20 11:30