settings for iSCSI root
AFAIK, open-e is based on an old kernel and an old version of IET, I'm
not sure how it reloads settings.
Last I used it, it needed full daemon restart and was not very reliable
- so the above link may not help you.
--
Tomasz Chmielewski
http://wpkg.org
to session 0, retcode 1 (115)
What does it mean? How can I make iscsistart work again (other than
downgrading)?
--
Tomasz Chmielewski
http://wpkg.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
open-iscsi group
Tomasz Chmielewski schrieb:
iscsistart: Could not read proc_name for host1 rc 5.
iscsi: invalid session 0
iscsistart: Received iferror -22
iscsistart: can't create connection (2)
iscsistart: Received iferror -22
iscsistart: can not safely destroy session 0
iscsistart: Received iferror -22
Tomasz Chmielewski schrieb:
Although when I start iscsid from any 2.0-870.x release, it drops the
connection started by iscsistart and is unable to reconnect (iscsid:
Could not verify connection 0:1. Dropping event.), until the device is
offlined.
Can it be that these problems happen
IET but we have never used IET mailing list for tgt.
FYI, our old mailing list is stgt-de...@lists.berlios.de.
Of course, my mistake.
--
Tomasz Chmielewski
http://wpkg.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
...@vger.kernel.org
--
Tomasz Chmielewski
http://wpkg.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group
Ben Greear schrieb:
When I create a session to a target, a /dev/sdX shows up. Is there
any way to know which /dev/sdX
a particular target is associated with?
Fdisk will show me a 'Disk identifier', maybe that could be set in
iscsi somehow?
Try:
ls -l /dev/disk/by-path/
--
Tomasz
Ulrich Windl schrieb:
On 9 Feb 2009 at 11:11, Tomasz Chmielewski wrote:
Is it safe to use swap over iSCSI?
Or will the system deadlock under memory pressure?
Why should a system deadlock? You mean iSCSI needs memory (for TCP transport)
to
page out, but getting that memory would
Host Mount /ora1
Look into /dev/disk/ and use these paths rather than /dev/sdX.
--
Tomasz Chmielewski
http://wpkg.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send
shorter names in
/dev/disk/by-id (no partitions though).
And if you want to use fstab, you probably want to use device labels (-L
option in tune2fs, mkswap, see man fstab).
--
Tomasz Chmielewski
http://wpkg.org
--~--~-~--~~~---~--~~
You received this message
which needs to access data on the target, but can't, because of
a network failure, will be put into an uninterruptible sleep until the
target is accessible again (or the timeout triggers, which means I/O error).
--
Tomasz Chmielewski
http://wpkg.org
.
--
Tomasz Chmielewski
http://wpkg.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email
Bart Van Assche schrieb:
On Fri, Jan 9, 2009 at 3:22 PM, Tomasz Chmielewski man...@wpkg.org wrote:
Bart Van Assche schrieb:
# ping -q -i 0.01 -c1000 -s160 ${remote_ip}
I get about 1% losses.
IMHO running iSCSI over a slow link should work, but a packet loss of
1% is troublesome
for
normal writes), start reading and writing...
I can reproduce it with tgtd and IET, so I guess open-iscsi is to be blamed.
Ideas what's wrong and why it fails?
--
Tomasz Chmielewski
http://wpkg.org
--~--~-~--~~~---~--~~
You received this message because you
, that's what I said in my previous mail (perhaps not clear enough):
You have to use a different drive for domU ;)
--
Tomasz Chmielewski
http://wpkg.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
open-iscsi group
--- swap
8 0 780200960 sda --- target
8 1 780196724 sda1 --- target (partition)
816 20480 sdb
Are you running Xen?
--
Tomasz Chmielewski
http://wpkg.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed
Carlos Acedo schrieb:
On 3 sep, 13:56, Tomasz Chmielewski [EMAIL PROTECTED] wrote:
Are you running Xen?
Yes, this is a domU, did you have the same problem?
Generally, it's a problem with Xen (running from upstream Xen 2.6.18
kernels). You have to use a different drive for domU.
You
).
--
Tomasz Chmielewski
http://wpkg.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email
:
iscsiadm -m node -T iqn.2007-05.net.my:store.backup -o update -n
node.session.timeo.replacement_timeout -v 120
--
Tomasz Chmielewski
http://wpkg.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
open-iscsi group
iSCSI).
--
Tomasz Chmielewski
http://wpkg.org
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send
aspasia schrieb:
On Apr 29, 1:10 pm, Tomasz Chmielewski [EMAIL PROTECTED] wrote:
aspasia schrieb:
If you're referring
tohttp://wpkg.org/Diskless_/_remote_boot_with_Open-iSCSI, rootfs is
currently hardcoded.
thanks ... yeah .. i remember your paper ... i am almost getting
Konrad Rzeszutek schrieb:
On Fri, May 02, 2008 at 04:33:42PM +0200, Tomasz Chmielewski wrote:
Konrad Rzeszutek schrieb:
shmget(IPC_PRIVATE, 52, IPC_CREAT|IPC_EXCL|0644) = -1 ENOSYS (Function
not implemented)
What OS under Xen are you running that doesn't have the shm* commands
implemented
aspasia schrieb:
On May 2, 7:14 am, Tomasz Chmielewski [EMAIL PROTECTED] wrote:
aspasia schrieb:
iSCSI initiators and dynamic IP address are two things which don't like
each other very much.
It will work if you add a dhclient to your initrd, but with any IP
address change you'll run
/cmdline (and passed upon PXE boot).
--
Tomasz Chmielewski
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
open-iscsi group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from
24 matches
Mail list logo