Christoph Anton Mitterer wrote (ao):
> May 19 03:25:50 lcg-lrz-dc10 kernel: [903106.581205] sd 0:0:14:0: Device
> offlined - not ready after error recovery
> May 28 16:38:43 lcg-lrz-dc10 kernel: [1727488.984810] sd 0:0:14:0: rejecting
> I/O to offline device
> May 28 16:39:19 lcg-lrz-dc10 kernel: [1727524.067182] BTRFS: lost page write
> due to I/O error on /dev/sdm
> May 28 16:39:19 lcg-lrz-dc10 kernel: [1727524.067426] BTRFS: bdev /dev/sdm
> errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
> May 28 21:03:06 lcg-lrz-dc10 kernel: [1743336.347191] sd 0:0:14:0: rejecting
> I/O to offline device
> May 28 21:03:06 lcg-lrz-dc10 kernel: [1743336.369569] BTRFS: lost page write
> due to I/O error on /dev/sdm
> Well as I've said,.. maybe it's not an issue at all, but at least it's
> strange that this happens on brand new hardware only with the
> btrfs-raid56 node, especially the gazillions of megasas messages.
Brand new hardware is most likely to show (hardware) issues as it has no
proven track record yet while it was subject to any kind of abuse during
transport. I'm sure you will see the same if you put sw raid + ext4 on
this server.
Nice hardware btw, please share your findings.
Sander
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
