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 extent
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 sessio
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 again
I'll try to get updated to the latest version. It will take time. In the
meantime, to answer your question, I am getting these closes in simple I/O
cases. Here is the first test unit ready and notice that the close was
almost immediate:
I->T ISID 00023D01, TSIH 0001, CID , CPE# 0, clo
Eddy Quicksall wrote:
> Sorry, the prints were in the syslog. The kernel is version
> 2.6.24-rc7bidi_02 #5 Fri Jun 6 13:12:08 EDT 2008 i686 i686 i386 GNU/Linux.
> The open-iscsi is version iscsiadm version 2.0-869. The code came from a 3rd
> party who supposedly got it from open-iscsi.org.
>
It
Also, may not have anything to do with it but when I peek at the
network with wireshark while writing to the drive, I see "TCP Checksum
Incorrect" from my computer to the tape drive.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the G
Sorry, the prints were in the syslog. The kernel is version
2.6.24-rc7bidi_02 #5 Fri Jun 6 13:12:08 EDT 2008 i686 i686 i386 GNU/Linux.
The open-iscsi is version iscsiadm version 2.0-869. The code came from a 3rd
party who supposedly got it from open-iscsi.org.
Here is a snip from syslog (note tha
Hi all,
I've been using open-iscsi to set up an IBM Ultrium LTO-4 tape drive.
I can connect and transfer files and everything, but the maximum read
or write speed I can get is like 16MB/s by tweaking the block size. I
am on a gigabit network, which the tape drive supports. The drive
specificati
Hey list,
I am traveling to Boston for Red Hat Summit this week, and I am not sure
what type of access to email I will have. If I do not answer your mail
with my usual quickness :) you know why, so please be patient and I will
get to all the emails by next Monday.
Thanks
Mike
--~--~
swejis wrote:
>> Up to the parts where you see the last scsi device get added.
>
> I previously posted this file: http://www.wehay.com/messages.1.gz wont
> that do ?
No. I do not need any of the kernel info. It all seems to be telling us
that the kernel really does think we set the timers as 5
Hello,
thanks for quick reply. During weekend I did backups on the iscsi-device
with not one single error on kernel 2.6.22.
Am Freitag, den 13.06.2008, 19:11 +0200 schrieb Mike Christie:
> Michael Kindermann wrote:
> > Hello,
> >
> > We receive errors below on a standard debian lenny/testing syt
11 matches
Mail list logo
