This email was quite interesting and made me think a little bit about
the world we live in...
(if you are talking about the 8 monkeys email)
Dotan
Nikhil Talpallikar wrote:
> Hi,
>
> Very sorry for the previous mail which was actually intended for a few
> people but somehow, by mistake got
On 09/10/2009 05:23 PM, Chiradeep Vittal wrote:
> Thanks. I'll take a look at the netlink interface. Not using multipath
> for now, but will do so later.
>
> For basic monitoring of storage network problems, here's what I am
> thinking:
> 1. If there is a network failure, eventually cat /sys/block
[BNX2I] Fix context mapping issue for architectures with PAGE_SIZE != 4096
* 5706/5708/5709 devices allow driver/user to set page size. By default
it is set to 4096
* Current drivers do not program this register based on architecture type
(e.g. x86 = 4K, IA64 = 16K) and by
Very enlightening, thanks.
If there is a constant stream of traffic over the iscsi session and
there is a network failure,
then the scsi eh timer should fire right?
And the disk will then go offline (according to /sys/block//
device/state )?
I think where this is leading to is to use dm-multipath
Thanks. I was looking for more granular error reporting
(i.e., iscsi session X failed at Y / iscsi session X had Y errors
between time A and time B)
On Sep 10, 11:24 pm, "Ulrich Windl" wrote:
> On 10 Sep 2009 at 10:53, solidguy wrote:
>
>
>
> > Is there a good way to monitor the iscsi sessions f
