persistent storage no longer mounting

[Ezra Kissel]

Experiment ibp0, aptvm069-1

The VM no longer mounts my persistent data set:
urn:publicid:IDN+apt.emulab.net:geni-pg0+dataset+geni-PG0:ibp_storage

VM has been rebooted a couple times. Is there an easy way to restore it
at this point?

I'm seeing this in the emulab logs:

Checking Testbed remote storage configuration ...
Checking 'bsnode'...
Configuring 'bsnode'...
*** Could not perform first-time initialization of block store bsnode
(uuid=iqn.2014-05.net.emulab.apt:geni-PG0:ibp0:bsnode), see
/var/emulab/logs/bsnode.out
*** Could not create storage device 'bsnode'
*** /usr/local/etc/emulab/rc/rc.storage:
Could not process storage commands!
Failed running rc.storageremote (2048)! at
/usr/local/etc/emulab/libsetup.pm line 1161.

and

New iSCSI node [tcp:[hw=,ip=,net_if=,iscsi_if=default]
10.254.254.254,3260,-1 iqn.2014-05.net.emulab.apt:geni-PG0:ibp0:bsnode]
added
iscsiadm: Could not login to [iface: default, target:
iqn.2014-05.net.emulab.apt:geni-PG0:ibp0:bsnode, portal:
10.254.254.254,3260].
iscsiadm: initiator reported error (8 - connection timed out)
iscsiadm: Could not log into all portals
Logging in to [iface: default, target:
iqn.2014-05.net.emulab.apt:geni-PG0:ibp0:bsnode, portal:
10.254.254.254,3260] (multiple)

bsnode is showing status as 'Changing' now, not sure why.

thanks,
- ezra

[Leigh Stoller]

> The VM no longer mounts my persistent data set: urn:publicid:IDN+apt.emulab.net:geni-pg0+dataset+geni-PG0:ibp_storage

Hi Ezra, one of the block store experts will take a look when they get into
the office. Sorry for the inconvenience.

Leigh

[Mike Hibler]

The 10G link between the storage server and the switch is down.
I am trying to find out why...

> --
> You received this message because you are subscribed to the Google Groups
> "cloudlab-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to cloudlab-user...@googlegroups.com.
> To post to this group, send email to cloudla...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/cloudlab-users/5710EB61.7000902%40indiana.edu.
> For more options, visit https://groups.google.com/d/optout.

[Mike Hibler]

Rebooting the storage server seems to have taken care of the problem.
I logged in to your node and re-ran the storage setup and you should
be good to go again.

> To view this discussion on the web visit https://groups.google.com/d/msgid/cloudlab-users/20160415140834.GB77778%40flux.utah.edu.