On Tue, Sep 24, 2013 at 09:43:45AM -0400, Vivek Goyal wrote:
[..]
> > > +kdump_is_ibft() {
A better name might be "target_is_ibft_lun()"
> > > + local path=$1
> > > + local tgt_name fw_tgt_name
> > > +
> > > + tgt_name=$(kdump_iscsi_get_rec_val "$path"
"node.name")
> > > + fw_tgt_name=$(/sbin/iscsiadm -m fw 2>/dev/null | awk '$1 ==
"node.name" {print $3}')
> > > +
> > > + [ -n "$fw_tgt_name" ] && strstr
"$fw_tgt_name" "$tgt_name"
I vaguely remember that one problem with ibft in the past was that one
could not tell reliably whether a lun came from ibft configuration or
not.
So how does above work. Can you give an actual example.
Is this generic enough to work on wide variety of iscsi ibft
configurations? So after this, should we start claiming supporting iscsi
using ibft as kdump target?
Thanks
Vivek