Alex M. wrote:
On Jun 16, 4:29 pm, Mike Christie [EMAIL PROTECTED] wrote:
Do:
iscsiadm -m session -r $SID --rescan
Doing a rescan doesn't appear to pick up the new size of the devices.
When you run that command what gets outputted to /var/log/messages. For
existing devices you should
On Jun 23, 1:27 pm, Mike Christie [EMAIL PROTECTED] wrote:
--snip--
However, there is issue outstanding I think. I think you then need a new
a newer kernel (like 2.6.26 or something) so that the block layer can
see the changes and pick up the scsi layer changes. Also see my comment
on FSs
On Jun 17, 7:00 am, Konrad Rzeszutek [EMAIL PROTECTED] wrote:
You can delete the old block devices that have changed and do a SCSI rescan:
You have to delete the old devices (well, this script deletes _ALL_ so that
might
not be that good):
for disk in `find
I have a Linux machine running as a target with LVM-backed devices and
the setup is working fine. However, when I change the size of one of
the underlying devices, the initiators (running open-iscsi 2.0-865)
don't pick up the change. I know that if I logout the entire session
and then log in
Alex M. wrote:
I have a Linux machine running as a target with LVM-backed devices and
the setup is working fine. However, when I change the size of one of
the underlying devices, the initiators (running open-iscsi 2.0-865)
don't pick up the change. I know that if I logout the entire session
On Jun 16, 4:29 pm, Mike Christie [EMAIL PROTECTED] wrote:
Do:
iscsiadm -m session -r $SID --rescan
Doing a rescan doesn't appear to pick up the new size of the devices.
Having manually resized the filesystem on the target end, I now get
errors on the initiator since the filesystem extents
