[Expired for open-iscsi (Ubuntu) because there has been no activity for
60 days.]
** Changed in: open-iscsi (Ubuntu)
Status: Incomplete => Expired
--
iscsid is looking for targets prior to network being available
https://bugs.launchpad.net/bugs/345957
You received this bug notification be
Just wanted to make obvious that my rc links given above are for rc0.d
and rc6.d .
--
iscsid is looking for targets prior to network being available
https://bugs.launchpad.net/bugs/345957
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Hi Peter,
I've forgotten my login for the bug tracking system on launchpad, but wanted
to respond to you as I've been thinking and testing along similar lines...
Only hours ago, I thought of trying the same thing on 9.04 that you just
tried on 9.10. At the moment I'm stuck on 9.04 since that is t
So for fun I rejigged the startup commands and it made my local setup
work. I doubt this is the proper way to go however.
lrwxrwxrwx 1 root root 18 2009-12-17 19:25 S33umountfs -> ../init.d/umountfs
lrwxrwxrwx 1 root root 20 2009-12-17 19:29 S34open-iscsi ->
../init.d/open-iscsi
lrwxrwxrwx 1 r
I want to specify that an iscsi volume can be attached on bootup and
shutdown with no problem.
Such a volume can also be mounted on bootup.
All this without any adjustments whatsoever (ex: changing the startup
links).
However, upon shutdown or reboot, if the volume happens to be mounted
then, an
** Attachment added: "iscsi_client_reboot-910-2.png"
http://launchpadlibrarian.net/37092003/iscsi_client_reboot-910-2.png
--
iscsid is looking for targets prior to network being available
https://bugs.launchpad.net/bugs/345957
You received this bug notification because you are a member of Ubu
Dustin,
I can confirm that an iscsi volume can be mounted automatically at boot
time for a Karmic client/initiator.
Now a reboot hangs terribly when such a volume is mounted. I've
attached a screenshot. It appears to confirm the comment above
(theterran wrote on 2009-06-15) where we need to scr
Peter-
I doubt we'll be able to fix this for Jaunty.
Can you confirm the bug on Karmic and Lucid?
:-Dustin
--
iscsid is looking for targets prior to network being available
https://bugs.launchpad.net/bugs/345957
You received this bug notification because you are a member of Ubuntu
Bugs, which
What other information is required to make this bug complete? Currently
in Jaunty you cannot mount iscsi volumes at boot time without stuffing a
mount command in /etc/rc.local.
--
iscsid is looking for targets prior to network being available
https://bugs.launchpad.net/bugs/345957
You received t
Ah, that should be "issue remains in jaunty". I'm using 9.04; better
with numbers...
open-iscsi version 2.0-870
--
iscsid is looking for targets prior to network being available
https://bugs.launchpad.net/bugs/345957
You received this bug notification because you are a member of Ubuntu
Bugs, whi
As of 2009.06.15 the issue remains in intrepid (2.6.28-11-server).
Moving S25open-iscsi to S50open-iscsi does not resolve the issue.
As a temporary workaround, I have added the following to /etc/rc.local
so that iSCSI volumes/devices configured with the _netdev option in
/etc/fstab are mounted aft
Hi,
I can confirm the same issue in ubuntu-server intrepid
mv /etc/rcS.d/S25open-iscsi /etc/rcS.d/S50open-iscsi do the trick
--
iscsid is looking for targets prior to network being available
https://bugs.launchpad.net/bugs/345957
You received this bug notification because you are a member of Ub
Setting it to S50open-iscsi didn't solve the issue for me.
--
iscsid is looking for targets prior to network being available
https://bugs.launchpad.net/bugs/345957
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Yes, I can mount the target right away once I login.
--
iscsid is looking for targets prior to network being available
https://bugs.launchpad.net/bugs/345957
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
@Ryan:
Are you able to login and mount the target manually?
The way iscsi is handled has changed in jaunty. They're considered as
normal block device, thus _netdev is not honored by the boot process.
** Changed in: open-iscsi (Ubuntu)
Status: New => Incomplete
--
iscsid is looking for t
I can confirm the same for Hardy, this works for me:
mv /etc/rcS.d/S25open-iscsi /etc/rcS.d/S50open-iscsi
--
iscsid is looking for targets prior to network being available
https://bugs.launchpad.net/bugs/345957
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I should add that I tried changing /etc/rcS.d/S25open-iscsi to S41open-
scsi (just after networking) and while I didn't get the [failed] message
the target still didn't automatically mount.
--
iscsid is looking for targets prior to network being available
https://bugs.launchpad.net/bugs/345957
Yo
** Attachment added: "screen shot"
http://launchpadlibrarian.net/24152989/photo.jpg
--
iscsid is looking for targets prior to network being available
https://bugs.launchpad.net/bugs/345957
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
18 matches
Mail list logo
