Comments on: I got your LUNs right here, pal http://number9.hellooperator.net/articles/2006/12/21/i-got-your-luns-right-here-pal a bird to bring my message home Fri, 11 Dec 2009 15:13:33 +0000 http://wordpress.org/?v=2.8.6 hourly 1 By: Dick http://number9.hellooperator.net/articles/2006/12/21/i-got-your-luns-right-here-pal/comment-page-1#comment-77813 Dick Sat, 17 Jan 2009 07:47:14 +0000 http://number9.hellooperator.net/articles/2006/12/21/i-got-your-luns-right-here-pal#comment-77813 Wow, that was a while ago :) But I think my plan was to name the clones in a standard way, so a iSCSI client would know that they could attach 'your-lun-monday' and get mondays volume. Like I said, it's much clankier than in-filesystem snapshots, but better than nothing. Wow, that was a while ago :)

But I think my plan was to name the clones in a standard way, so a iSCSI client would know that they could attach ‘your-lun-monday’ and get mondays volume.

Like I said, it’s much clankier than in-filesystem snapshots, but better than nothing.

]]> By: Avi Deitcher http://number9.hellooperator.net/articles/2006/12/21/i-got-your-luns-right-here-pal/comment-page-1#comment-70934 Avi Deitcher Fri, 19 Dec 2008 19:02:47 +0000 http://number9.hellooperator.net/articles/2006/12/21/i-got-your-luns-right-here-pal#comment-70934 Dick, Can you explain what you mean by: "Adding zfs set readonly=on tank/iscsi/sinister gets you the benefit of the .zfs/snapshot directory NFS clients would see if you’d set sharenfs=on (OK, you’re sharing a snapshot of the entire LUN rather than the filesystem, but clients can still get their old files without bugging you, so it does the job)." How does this work to get clients to see their stuff without bugging you? sinister is a clone of a snapshot of lefty. If this were straight zfs (including filesystem), then any client could just go to .zfs/snapshot under their volume and get the data. For iSCSI, they are mounting lefty as a single iSCSI target. How do you get them to see the other snapshots? Thanks. Dick,

Can you explain what you mean by:

“Adding
zfs set readonly=on tank/iscsi/sinister
gets you the benefit of the .zfs/snapshot directory NFS clients would see if you’d set sharenfs=on (OK, you’re sharing a snapshot of the entire LUN rather than the filesystem, but clients can still get their old files without bugging you, so it does the job).”

How does this work to get clients to see their stuff without bugging you? sinister is a clone of a snapshot of lefty. If this were straight zfs (including filesystem), then any client could just go to .zfs/snapshot under their volume and get the data. For iSCSI, they are mounting lefty as a single iSCSI target. How do you get them to see the other snapshots?

Thanks.

]]> By: Dick Davies http://number9.hellooperator.net/articles/2006/12/21/i-got-your-luns-right-here-pal/comment-page-1#comment-22 Dick Davies Thu, 21 Dec 2006 13:59:00 +0000 http://number9.hellooperator.net/articles/2006/12/21/i-got-your-luns-right-here-pal#comment-22 Can't be sure, but I don't see how sparse volumes could work otherwise. Can’t be sure, but I don’t see how sparse volumes could work otherwise.

]]> By: Ceri Davies http://number9.hellooperator.net/articles/2006/12/21/i-got-your-luns-right-here-pal/comment-page-1#comment-21 Ceri Davies Thu, 21 Dec 2006 11:58:41 +0000 http://number9.hellooperator.net/articles/2006/12/21/i-got-your-luns-right-here-pal#comment-21 So now they're not zero-filled? Cool. So now they’re not zero-filled? Cool.

]]>