ZFS + iSCSI architecture
Hello, I am about to start deploying a large system (about 18 To which can grow up to 36 To) based on a big Intel platform with lot's of fancy features to have turbo boosted platform (ZIL on SSD + system on dongle if I go for FreeNAS). Since I want to move on quite fast I might decide to use FreeNAS in it's latest version. The idea behind all that was to grant 5 or six critical servers access to the NAS so that they can take advantage of : 1. space available on the NAS 2. ability of the NAS to use ZFS and of clients to support this file system (including snapshots) 3. Access the server using iSCSI (at least this is what I initially planned). 4. Mount part of their filesystem using data stored on the SAN (like /usr/local/ or other parts of the system). The server accessing the data will be of two types : 1. 2 x Ubuntu server 10.04 LTS 2. 4 x FreeBSD (mainly 8 and 9) with jail configured I have started reading about iSCSI and potential problems with FreeBSD. So my main questions would be : • Should I go for iSCSI ? • Should I rather choose / prefer NFS ? • Should I export a Volume as UFS rather than ZFS (is ZFS supported as a target) ? The main idea is stability, redundancy of data and ease of maintenance (in a headless FreeBSD / Linux world) before anything else ! That's the big pictures, if you have any pointers, advise, they are all welcome. It is quite late where I leave, so I will reply to posts in 8 to 10 hours, but I hope to have enough answer(s) to start an interesting thread (as I think this question is very interesting and not so clearly explained (at least in my mind))… Thx very much for your infos and feedback. «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ BSD - BSD - BSD - BSD - BSD - BSD - BSD - BSD - «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ PGP ID -- 0x1BA3C2FD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS + iSCSI architecture
On 19-02-2013, Tue [23:20:41], b...@todoo.biz wrote: Hello, I am about to start deploying a large system (about 18 To which can grow up to 36 To) based on a big Intel platform with lot's of fancy features to have turbo boosted platform (ZIL on SSD + system on dongle if I go for FreeNAS). Since I want to move on quite fast I might decide to use FreeNAS in it's latest version. The idea behind all that was to grant 5 or six critical servers access to the NAS so that they can take advantage of : 1. space available on the NAS 2. ability of the NAS to use ZFS and of clients to support this file system (including snapshots) 3. Access the server using iSCSI (at least this is what I initially planned). 4. Mount part of their filesystem using data stored on the SAN (like /usr/local/ or other parts of the system). The server accessing the data will be of two types : 1. 2 x Ubuntu server 10.04 LTS 2. 4 x FreeBSD (mainly 8 and 9) with jail configured I have started reading about iSCSI and potential problems with FreeBSD. So my main questions would be : • Should I go for iSCSI ? • Should I rather choose / prefer NFS ? • Should I export a Volume as UFS rather than ZFS (is ZFS supported as a target) ? The main idea is stability, redundancy of data and ease of maintenance (in a headless FreeBSD / Linux world) before anything else ! That's the big pictures, if you have any pointers, advise, they are all welcome. It is quite late where I leave, so I will reply to posts in 8 to 10 hours, but I hope to have enough answer(s) to start an interesting thread (as I think this question is very interesting and not so clearly explained (at least in my mind))… Thx very much for your infos and feedback. Hello, If I needed a NFS+iSCSI solution I'd go for Solaris 11. Docs are abundant and the system is very stable and feature-rich. Tried recently the integration in Windows Domain and iSCSI features, all works wery good. Don't get me wrong, I'm all for FreeBSD ;) but in this particular case I'd choose Solaris. -- D.S. -\ Powered by ---o -/ FreeBSD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS + iSCSI architecture
On Feb 19, 2013, at 11:20 PM, b...@todoo.biz b...@todoo.biz wrote: Hello, I am about to start deploying a large system (about 18 To which can grow up to 36 To) based on a big Intel platform with lot's of fancy features to have turbo boosted platform (ZIL on SSD + system on dongle if I go for FreeNAS). Since I want to move on quite fast I might decide to use FreeNAS in it's latest version. The idea behind all that was to grant 5 or six critical servers access to the NAS so that they can take advantage of : 1. space available on the NAS 2. ability of the NAS to use ZFS and of clients to support this file system (including snapshots) 3. Access the server using iSCSI (at least this is what I initially planned). 4. Mount part of their filesystem using data stored on the SAN (like /usr/local/ or other parts of the system). The server accessing the data will be of two types : 1. 2 x Ubuntu server 10.04 LTS 2. 4 x FreeBSD (mainly 8 and 9) with jail configured I have started reading about iSCSI and potential problems with FreeBSD. What problems do you mean ? So my main questions would be : • Should I go for iSCSI ? Well in all use cases, iscsi should perform faster than NFS. • Should I rather choose / prefer NFS ? • Should I export a Volume as UFS rather than ZFS (is ZFS supported as a target) ? I'm not sure what you mean here, when you export a zvol over ISCSI: - your SAN is the target and presents a block device (the zvol) - your client is the initiator - your client attaches to the ISCSI drive and formats it using filesystem XYZ, be it ext3, ufs or ntfs The main idea is stability, redundancy of data and ease of maintenance (in a headless FreeBSD / Linux world) before anything else ! ISCSI is a bit harder to setup IMO, however I think it''s more reliable than NFS, what with its auto retries if it loses the network link to a device. That's the big pictures, if you have any pointers, advise, they are all welcome. It is quite late where I leave, so I will reply to posts in 8 to 10 hours, but I hope to have enough answer(s) to start an interesting thread (as I think this question is very interesting and not so clearly explained (at least in my mind))… This is idd a very interesting topic and I hope to see more :) Thx very much for your infos and feedback. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS + iSCSI architecture
Sounds like a major headache. I'd just deploy NetApp with OnTap 8.X or isilon, both BSD based now. On Feb 19, 2013 7:15 PM, Fleuriot Damien m...@my.gd wrote: On Feb 19, 2013, at 11:20 PM, b...@todoo.biz b...@todoo.biz wrote: Hello, I am about to start deploying a large system (about 18 To which can grow up to 36 To) based on a big Intel platform with lot's of fancy features to have turbo boosted platform (ZIL on SSD + system on dongle if I go for FreeNAS). Since I want to move on quite fast I might decide to use FreeNAS in it's latest version. The idea behind all that was to grant 5 or six critical servers access to the NAS so that they can take advantage of : 1. space available on the NAS 2. ability of the NAS to use ZFS and of clients to support this file system (including snapshots) 3. Access the server using iSCSI (at least this is what I initially planned). 4. Mount part of their filesystem using data stored on the SAN (like /usr/local/ or other parts of the system). The server accessing the data will be of two types : 1. 2 x Ubuntu server 10.04 LTS 2. 4 x FreeBSD (mainly 8 and 9) with jail configured I have started reading about iSCSI and potential problems with FreeBSD. What problems do you mean ? So my main questions would be : • Should I go for iSCSI ? Well in all use cases, iscsi should perform faster than NFS. • Should I rather choose / prefer NFS ? • Should I export a Volume as UFS rather than ZFS (is ZFS supported as a target) ? I'm not sure what you mean here, when you export a zvol over ISCSI: - your SAN is the target and presents a block device (the zvol) - your client is the initiator - your client attaches to the ISCSI drive and formats it using filesystem XYZ, be it ext3, ufs or ntfs The main idea is stability, redundancy of data and ease of maintenance (in a headless FreeBSD / Linux world) before anything else ! ISCSI is a bit harder to setup IMO, however I think it''s more reliable than NFS, what with its auto retries if it loses the network link to a device. That's the big pictures, if you have any pointers, advise, they are all welcome. It is quite late where I leave, so I will reply to posts in 8 to 10 hours, but I hope to have enough answer(s) to start an interesting thread (as I think this question is very interesting and not so clearly explained (at least in my mind))… This is idd a very interesting topic and I hope to see more :) Thx very much for your infos and feedback. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS + iSCSI architecture
Le 20 févr. 2013 à 02:14, Fleuriot Damien m...@my.gd a écrit : On Feb 19, 2013, at 11:20 PM, b...@todoo.biz b...@todoo.biz wrote: Hello, I am about to start deploying a large system (about 18 To which can grow up to 36 To) based on a big Intel platform with lot's of fancy features to have turbo boosted platform (ZIL on SSD + system on dongle if I go for FreeNAS). Since I want to move on quite fast I might decide to use FreeNAS in it's latest version. The idea behind all that was to grant 5 or six critical servers access to the NAS so that they can take advantage of : 1. space available on the NAS 2. ability of the NAS to use ZFS and of clients to support this file system (including snapshots) 3. Access the server using iSCSI (at least this is what I initially planned). 4. Mount part of their filesystem using data stored on the SAN (like /usr/local/ or other parts of the system). The server accessing the data will be of two types : 1. 2 x Ubuntu server 10.04 LTS 2. 4 x FreeBSD (mainly 8 and 9) with jail configured I have started reading about iSCSI and potential problems with FreeBSD. What problems do you mean ? For example : - Can my client (the initiator) directly mount a ZFS volume on freeBSD using iSCSI or should I go back to formatting It to UFS ? - Is the iSCSI stack in FreeBSD stable an mature enough to be used in a production environment ? == It is out of scope to have kernel panic because of an unstable iSCSI related problem. So my main questions would be : • Should I go for iSCSI ? Well in all use cases, iscsi should perform faster than NFS. Fast is good - stable is necessary in this case ! And this is what I am tring to evaluate… • Should I rather choose / prefer NFS ? • Should I export a Volume as UFS rather than ZFS (is ZFS supported as a target) ? I'm not sure what you mean here, when you export a zvol over ISCSI: - your SAN is the target and presents a block device (the zvol) - your client is the initiator - your client attaches to the ISCSI drive and formats it using filesystem XYZ, be it ext3, ufs or ntfs Thanks for this reminder about vocabulary for iSCSI, I'll try to stick to It ;-) The main idea is stability, redundancy of data and ease of maintenance (in a headless FreeBSD / Linux world) before anything else ! ISCSI is a bit harder to setup IMO, however I think it''s more reliable than NFS, what with its auto retries if it loses the network link to a device. Have you deployed this in production and what are your concerns and recommendations ? That's the big pictures, if you have any pointers, advise, they are all welcome. It is quite late where I leave, so I will reply to posts in 8 to 10 hours, but I hope to have enough answer(s) to start an interesting thread (as I think this question is very interesting and not so clearly explained (at least in my mind))… This is idd a very interesting topic and I hope to see more :) There is also an interesting (and fresh) post here : http://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSFreeBSDvsIllumos?showcomments#comments Thx very much for your infos and feedback. «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ BSD - BSD - BSD - BSD - BSD - BSD - BSD - BSD - «?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§«?»¥«?»§ PGP ID -- 0x1BA3C2FD ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Freebsd iSCSI client ?
On 2012-10-29 17:08, dweimer wrote:
On 2012-10-29 13:51, dweimer wrote:
On 2012-10-29 08:29, John Levine wrote:
I'm trying to set up a freebsd image under vmware, but I need more
disk
space than the vmware hosts offer. So the guy who runs the hosting
place
suggests getting a 1U disk server and using iSCSI over gigabit
Ethernet
so I can build zfs volumes from the iSCSI disks.
Poking around, the reports say that FreeBSD is a pretty good iSCSI
server in such forms as freenas, but a lousy iSCSI client, with the
first problem being that that kludges are required to get iSCSI
volumes mounted early enough in the boot process for ZFS to find
them.
Is this still the case in FreeBSD 9?
I'd rather not use NFS, since the remote disks have mysql
databases,
and mysql and NFS are not friends.
An alternative is to mount the iSCSI under vmware, so zfs sees them
as
normal disks. Anyone tried that?
TIA,
John
I don't have an answer for you at the moment, but I can tell you
that
I just started a new server build this morning with the intent of
using it as an iSCSI client and running ZFS on the drive. In my
case
however its going to be a file server that doesn't have very much
heavy I/O, with the intention of using compression on the ZFS file
set. In my case a script ran after start up to mount the drive
would
work if it fails. I will let you know what I find out, server is in
the middle of a buildworld to get it updated to the p4 release.
Yes you can mount as a drive through VMware and use ZFS just fine, I
have done a lot of recent tests using ZFS as the boot volume under
VMware. This new server will be my first production server to use
what
I have learned from those tests, as its system drive mounted through
VMware (ESX 4.1) and is booting from ZFS. Once the install of the
buildworld is complete I will add a 150G ZFS data set on our HP
Lefthand Networks SAN, run some tests and let you know the outcome
of
them.
Looks like I have some learning to do, system is up and running and
talks to the iscsi volume just fine, however as you mentioned, the
big
problem is mounting the volume at start up. can't find any options
at
all to launch iscontrol at boot. Found an example
/usr/local/etc/rc.d/ script from a mail forum a ways back however it
was setup to use UFS volumes and a secondary fstab file for the iscsi
volumes. I don't see any reason that one can't be made to make use
of
zfs with the volumes set with option canmount=noauto and using an
rc.conf variable to pass which volumes to mount at boot, and umount
at
shutdown to the script.
However, I have some reading to do before I get started, as I haven't
tried to create an rc.d script, and need to get an understanding of
how to properly create one which follows all the proper guidelines,
and allows itself to be a requirement for other scripts. I don't see
any reason it would work successfully to host a MySQL database as the
OP was looking for or a Samba share as I intend to use it as long as
their start up can be set to require the iSCSI start up to run first.
If anyone has already done something similar to this and has some
information to pass on that would be great. I probably won't have
time to even start researching this till Thursday this week
Well I got stuck waiting at work today for a replacement array
controller, and got some time to work on this. This still needs some
work, and I am not sure its the best way to handle it as it does an
export on the zpool at shutdown and import at start up. I also don't
know at this point about other services waiting on it. But I have
verified that a server reboot cleanly dismounts the volumes and a reboot
remounts them.
Things to note, the # BEFORE: line below, that was copied from the old
mailing list thread I found, not sure if that is something real or not.
The ZFS data set I was using was set with option canmount=noauto. the
zpool import/export and zfs mount/umount are just typed in there, it
needs to be broken up and pulled form an rc.conf variable option instead
#!/bin/sh
# PROVIDE: iscsi
# REQUIRE: NETWORKING
# BEFORE: mountcritremote
# KEYWORD: shutdown
. /etc/rc.subr
name=iscsi
start_cmd=iscsi_start
stop_cmd=iscsi_stop
rcvar=iscsi_enable
required_modules=iscsi_initiator:iscsi
iscsi_start() {
${iscsi_command} -c ${iscsi_config} -n ${iscsi_nickname}
sleep 1
zpool import ziscsi
zfs mount ziscsi/storage
}
iscsi_stop() {
zfs umount ziscsi/storage
zpool export ziscsi
killall -HUP ${iscsi_command}
}
load_rc_config $name
: ${iscsi_enable=NO}
: ${iscsi_command=iscontrol}
: ${iscsi_config=/etc/iscsi.conf}
: ${iscsi_nickname=}
run_rc_command $1
Other files information used:
rc.conf:
...
# Enable iscsi
iscsi_enable=YES
iscsi_command=iscontrol
iscsi_nickname=LHMG002
iscsi_config=/etc/iscsi.conf
...
iscsi.conf:
# Globals
port = 3260
InitiatorName = iqn.2005-01.il.ac.huji.cs:testvm.local
LHMG002 {
TargetAddress = 10.31.120.102:3260,1
Re: Freebsd iSCSI client ?
On 2012-10-29 08:29, John Levine wrote: I'm trying to set up a freebsd image under vmware, but I need more disk space than the vmware hosts offer. So the guy who runs the hosting place suggests getting a 1U disk server and using iSCSI over gigabit Ethernet so I can build zfs volumes from the iSCSI disks. Poking around, the reports say that FreeBSD is a pretty good iSCSI server in such forms as freenas, but a lousy iSCSI client, with the first problem being that that kludges are required to get iSCSI volumes mounted early enough in the boot process for ZFS to find them. Is this still the case in FreeBSD 9? I'd rather not use NFS, since the remote disks have mysql databases, and mysql and NFS are not friends. An alternative is to mount the iSCSI under vmware, so zfs sees them as normal disks. Anyone tried that? TIA, John I don't have an answer for you at the moment, but I can tell you that I just started a new server build this morning with the intent of using it as an iSCSI client and running ZFS on the drive. In my case however its going to be a file server that doesn't have very much heavy I/O, with the intention of using compression on the ZFS file set. In my case a script ran after start up to mount the drive would work if it fails. I will let you know what I find out, server is in the middle of a buildworld to get it updated to the p4 release. Yes you can mount as a drive through VMware and use ZFS just fine, I have done a lot of recent tests using ZFS as the boot volume under VMware. This new server will be my first production server to use what I have learned from those tests, as its system drive mounted through VMware (ESX 4.1) and is booting from ZFS. Once the install of the buildworld is complete I will add a 150G ZFS data set on our HP Lefthand Networks SAN, run some tests and let you know the outcome of them. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Anyone Tried to use iPXE to boot with iSCSI?
- Original Message - From: Paul Wootton cas...@caspersworld.co.uk To: Bill Tillman btillma...@yahoo.com Cc: Sent: Thursday, September 20, 2012 4:08 AM Subject: Re: Anyone Tried to use iPXE to boot with iSCSI? On 09/20/12 01:42, Bill Tillman wrote: Interesting project you've got there. I can't say mine is similar but I do have a machine which I'm using as a router which boots disklessly. Running 8.3-STABLE amd64, in fact I just rebuilt the world on both the server which serves this puppy it's OS and the /diskless partition where this puppy get's it's boot up from. Booting by pxe is not an easy thing to do. The docs are terrible and out of synch with the latest versions of the OS. I think there may have been some improvments on that end but it's still kind of a seat of the pants operation. I had several contacts in #FreeBSD on FreeNode who told me they had many diskless servers running yet when pressed for how they did it the answers they gave were vague and ambiguous, that is if they answered at all. I did finally find a site which explained most of it in an almost clear manner, but even that site was filled with typos and out of date information. The router I've built is great...no disks at all and until the reboot a few weeks ago it had been running 24/7 for 276 days...without one failure. We watch lots of NetFlix movies here, sometimes two or three at a time with my teenage kids here with their laptops. And I can still enjoy a quick download or two in my lab while all this bandwidth is being served. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Hi Bil,, I am actually looking at doing something very similar with my soekris box. Currently it boots from a CF card, but the card is getting old and I think it is coming to the end of it's life. Can you please shed a little light on what you did? Cheers Paul This is the website where I found the best and most accurate information on diskless booting. http://www.nber.org/sys-admin/FreeBSD-diskless.html The authors appear to have updated this just a few months ago as well. I had trouble with it until I understood what the conf/ folders were all about. It's easy for a novice to read this and get confused because the authors assume the reader knows as much about it as they do or they are just lazy hacks like me and don't want to type all the real meat of the setup. I wrote an e-mail to them and explained several typos they had in their article in 2010 when I first found this article. The guy who replied back was very cool and he thanked me for helping with some of the corrections. I read lots of other stuff, including the FreeBSD handbook but as usual it was not in synch with the newest releases and I couldn't get it working. I'm happy to say that now I have a wonderful diskless setup which I can update when I want toI don't think I'm going to go past 8.3-STABLE with it. The new 9.x-RELEASE uses a new drive format which has created problems for me with the older equipment I have around here. I'm finally throwing out most of the old stuff I've had for years around here. Just built two new Windows 7 workstations with i7 Quad cores and 16 GB RAM. These older servers are still working fine for me and I plan on using them until they drop. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Anyone Tried to use iPXE to boot with iSCSI?
On 19/09/2012 06:53, dweimer wrote: I was just trying some proof of concept testing to see if I could get a system booting with no local disk using iSCSI running from my FreeNAS box. I got started, by first booting a 9.1-RC1 CD, into live CD, created a /tmp/iscsi.conf used kldload to load the iscsi initiator, connected to the target, created a gpt boot partition, swap partition and just a single / volume using remianing space. Copied the bootcode, created the file system, extracted the system etc. Created a loader.conf file, added the iscsi_initiator_load=YES option, copied my /tmp/iscsi.conf file to the new file system at /etc/iscsi.conf created a /etc/fstab file using the gpart labels to mount / and swap partitions. Booted the system from the iPXE.iso, ran the necessary configuration options, connected to the iscsi volume, and booted from it. It does launch the bootcode, as expected, and then breaks failing to mount root. Whoch I actually expected, I have proved I can install to an iSCSI volume, I can connect to that iSCSI volume prior to loading the kernel, and load the kernel from it. What I can't seem to find any information on is how to mount iSCSI volumes at boot on FreeBSD, so that the kernel can mount the root partition. Does anyone have any idea how to do this, or if its even possible? Sounds like you need this http://freebsd.1045724.n5.nabble.com/iSCSI-boot-driver-0-2-5-isboot-ko-has-been-released-td5736301.html Vince ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Anyone Tried to use iPXE to boot with iSCSI?
On 2012-09-20 09:42, Vincent Hoffman wrote: On 19/09/2012 06:53, dweimer wrote: I was just trying some proof of concept testing to see if I could get a system booting with no local disk using iSCSI running from my FreeNAS box. I got started, by first booting a 9.1-RC1 CD, into live CD, created a /tmp/iscsi.conf used kldload to load the iscsi initiator, connected to the target, created a gpt boot partition, swap partition and just a single / volume using remianing space. Copied the bootcode, created the file system, extracted the system etc. Created a loader.conf file, added the iscsi_initiator_load=YES option, copied my /tmp/iscsi.conf file to the new file system at /etc/iscsi.conf created a /etc/fstab file using the gpart labels to mount / and swap partitions. Booted the system from the iPXE.iso, ran the necessary configuration options, connected to the iscsi volume, and booted from it. It does launch the bootcode, as expected, and then breaks failing to mount root. Whoch I actually expected, I have proved I can install to an iSCSI volume, I can connect to that iSCSI volume prior to loading the kernel, and load the kernel from it. What I can't seem to find any information on is how to mount iSCSI volumes at boot on FreeBSD, so that the kernel can mount the root partition. Does anyone have any idea how to do this, or if its even possible? Sounds like you need this http://freebsd.1045724.n5.nabble.com/iSCSI-boot-driver-0-2-5-isboot-ko-has-been-released-td5736301.html Vince That's looking promising, I had actually ran across an earlier version of this last night, of course that was all dealing with 8.1. Will definitely do more looking into it, however it doesn't seem to be at a point I would consider running anything more than a test environment from it. My actual goal with this project if the proof of concept panned out was to replace the old aging internal SATA Mirrored drives in my Home web/email server (They are showing a decent number of smart pre-fail indicators, but still working for now). I have fairly new SATA drives in my FreeNAS box, and thought maybe since my Gig network is barely being taxed, that I could save some cash for new disk drives, to be put towards future upgrades to the FreeNAS box instead. However I am not ruling out the possibility altogether yet, and am going to run some tests with booting from a very minimal set of required files on a USB thumb Drive, and mounting everything else from iSCSI. I am already running all my VMware Test Virtual Machines on my workstation from an iSCSI volume mounted from my FreeNAS box, and know that it performs well enough in my network to handle the small amount of traffic to my website and my email without any problems. -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Anyone Tried to use iPXE to boot with iSCSI?
I was just trying some proof of concept testing to see if I could get a system booting with no local disk using iSCSI running from my FreeNAS box. I got started, by first booting a 9.1-RC1 CD, into live CD, created a /tmp/iscsi.conf used kldload to load the iscsi initiator, connected to the target, created a gpt boot partition, swap partition and just a single / volume using remianing space. Copied the bootcode, created the file system, extracted the system etc. Created a loader.conf file, added the iscsi_initiator_load=YES option, copied my /tmp/iscsi.conf file to the new file system at /etc/iscsi.conf created a /etc/fstab file using the gpart labels to mount / and swap partitions. Booted the system from the iPXE.iso, ran the necessary configuration options, connected to the iscsi volume, and booted from it. It does launch the bootcode, as expected, and then breaks failing to mount root. Whoch I actually expected, I have proved I can install to an iSCSI volume, I can connect to that iSCSI volume prior to loading the kernel, and load the kernel from it. What I can't seem to find any information on is how to mount iSCSI volumes at boot on FreeBSD, so that the kernel can mount the root partition. Does anyone have any idea how to do this, or if its even possible? -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Anyone Tried to use iPXE to boot with iSCSI?
- Original Message - From: dweimer dwei...@dweimer.net To: FreeBSD Questions freebsd-questions@freebsd.org Cc: Sent: Wednesday, September 19, 2012 1:53 AM Subject: Anyone Tried to use iPXE to boot with iSCSI? I was just trying some proof of concept testing to see if I could get a system booting with no local disk using iSCSI running from my FreeNAS box. I got started, by first booting a 9.1-RC1 CD, into live CD, created a /tmp/iscsi.conf used kldload to load the iscsi initiator, connected to the target, created a gpt boot partition, swap partition and just a single / volume using remianing space. Copied the bootcode, created the file system, extracted the system etc. Created a loader.conf file, added the iscsi_initiator_load=YES option, copied my /tmp/iscsi.conf file to the new file system at /etc/iscsi.conf created a /etc/fstab file using the gpart labels to mount / and swap partitions. Booted the system from the iPXE.iso, ran the necessary configuration options, connected to the iscsi volume, and booted from it. It does launch the bootcode, as expected, and then breaks failing to mount root. Whoch I actually expected, I have proved I can install to an iSCSI volume, I can connect to that iSCSI volume prior to loading the kernel, and load the kernel from it. What I can't seem to find any information on is how to mount iSCSI volumes at boot on FreeBSD, so that the kernel can mount the root partition. Does anyone have any idea how to do this, or if its even possible? -- Thanks, Dean E. Weimer http://www.dweimer.net/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Interesting project you've got there. I can't say mine is similar but I do have a machine which I'm using as a router which boots disklessly. Running 8.3-STABLE amd64, in fact I just rebuilt the world on both the server which serves this puppy it's OS and the /diskless partition where this puppy get's it's boot up from. Booting by pxe is not an easy thing to do. The docs are terrible and out of synch with the latest versions of the OS. I think there may have been some improvments on that end but it's still kind of a seat of the pants operation. I had several contacts in #FreeBSD on FreeNode who told me they had many diskless servers running yet when pressed for how they did it the answers they gave were vague and ambiguous, that is if they answered at all. I did finally find a site which explained most of it in an almost clear manner, but even that site was filled with typos and out of date information. The router I've built is great...no disks at all and until the reboot a few weeks ago it had been running 24/7 for 276 days...without one failure. We watch lots of NetFlix movies here, sometimes two or three at a time with my teenage kids here with their laptops. And I can still enjoy a quick download or two in my lab while all this bandwidth is being served. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Pointers to debugging slow iSCSI initiator performance
Folks
I have a FreeBSD 8.1-STABLE system that I'm connecting via iSCSI to a
Compellent SAN. The iscsi-initiator works fine but is very slow and given
to periodic (very short) hangs. The issue is that we have subversion on
it and it takes a long time to checkout some of our repos. Any pointers to
tweaking the config or figuring out the cause of the slowness is
appreciated. I haven't found many posts about the iscsi-initiator on
FreeBSD in my searches.
The config is below:
arachnophile# dd if=/dev/zero of=/san/test.out bs=1M count=2048
2048+0 records in
2048+0 records out
2147483648 bytes transferred in 145.111894 secs (14798812 bytes/sec)
arachnophile# uname -a
FreeBSD arachnophile.virtc.com 8.1-STABLE FreeBSD 8.1-STABLE #0: Wed Oct
13 13:52:31 EDT 2010
r...@arachnophile.virtc.com:/usr/obj/usr/src/sys/ARACHNOPHILE amd64
arachnophile# more /etc/iscsi.conf
compellent {
initiatorname = arach
TargetName =
iqn.2002-03.com.compellent:5d3100067001
TargetAddress = 172.30.0.10:3260,0
}
Hardware (in case it matters) is an IBM xSeries 346
CPU: Intel(R) Xeon(TM) CPU 3.40GHz (3400.16-MHz K8-class CPU)
real memory = 2147483648 (2048 MB)
arachnophile# netstat -I bge1
NameMtu Network Address Ipkts Ierrs IdropOpkts
Oerrs Coll
bge1 1500 Link#2 00:14:5e:2b:39:7d 353438253 0 0
438355075 0 0
bge1 1500 172.30.0.0172.30.0.66 353316523 - -
438348928 - -
Thanks
Viren Shah
vs...@raytheonvtc.com
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: 3par iscsi with 8.2?
iqn = iqn.2010-09.com.enovafinancial:01:nut.postgres01 authmethod = none I think you don't need such lines in iscsi.conf Login session: postgres01# iscontrol -v -n path1 After that what do you see in 'dmesg -a'? And do you have logs at the iscsi target (3par)? -- View this message in context: http://freebsd.1045724.n5.nabble.com/3par-iscsi-with-8-2-tp4306095p4312612.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: 3par iscsi with 8.2?
Original Message-
From: owner-freebsd-questi...@freebsd.org
[mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of timp
Sent: Saturday, April 16, 2011 1:25 PM
To: freebsd-questions@freebsd.org
Subject: Re: 3par iscsi with 8.2?
No, I`m not. But have some experience in iscsi.
What kind of trouble do you have?
[Ragona, Derek]
Here is the configuration and Systems calls trace output:
Conf:
path1 {
targetaddress= 10.44.2.20
targetname = iqn.2000-05.com.3pardata:22110002ac000aba
iqn = iqn.2010-09.com.enovafinancial:01:nut.postgres01
initiatorName = iqn.2010-09.com.enovafinancial:01:nut.postgres01
authmethod = none
tags = 256
}
Discovery session:
postgres01# iscontrol -v -n path1 -d
port = 3260
tags = 256
maxluns = 0
iqn = iqn.2010-09.com.enovafinancial:01:nut.postgres01
maxConnections = 1
maxRecvDataSegmentLength = 65536
maxXmitDataSegmentLength = 65536
maxBurstLength = 131072
firstBurstLength = 65536
defaultTime2Wait = 0
defaultTime2Retain = 0
maxOutstandingR2T = 1
errorRecoveryLevel = 0
targetPortalGroupTag = 0
headerDigest = None,CRC32C
dataDigest = None,CRC32C
initialR2T = 1
immediateData = 1
dataPDUInOrder = 1
dataSequenceInOrder = 1
sessionType = Normal
targetAddress = 10.44.2.20
targetAlias = (null)
targetName = iqn.2000-05.com.3pardata:22110002ac000aba
initiatorName = iqn.2010-09.com.enovafinancial:01:nut.postgres01
initiatorAlias = (null)
authMethod = none
chapSecret = (null)
chapIName = (null)
tgtChapName = (null)
tgtChapSecret = (null)
tgttgtChallengeLen = 0
I-: cmd=0x3 len=310
SessionType=Discovery
InitiatorName=iqn.2010-09.com.enovafinancial:01:nut.postgres01
MaxBurstLength=131072
HeaderDigest=None,CRC32C
DataDigest=None,CRC32C
MaxRecvDataSegmentLength=65536
ErrorRecoveryLevel=0
DefaultTime2Wait=0
DefaultTime2Retain=0
DataPDUInOrder=Yes
DataSequenceInOrder=Yes
MaxOutstandingR2T=1
T-: cmd=0x23 len=269
TargetPortalGroupTag=211
MaxBurstLength=131072
HeaderDigest=None
DataDigest=None
MaxRecvDataSegmentLength=65536
ErrorRecoveryLevel=0
DefaultTime2Wait=2
DefaultTime2Retain=20
DataPDUInOrder=Yes
DataSequenceInOrder=Yes
MaxOutstandingR2T=1
InitialR2T=Yes
ImmediateData=No
I-: cmd=0x4 len=16
SendTargets=All
T-: cmd=0x24 len=87
TargetName=iqn.2000-05.com.3pardata:22110002ac000aba
TargetAddress=10.44.2.20:3260,211
TargetName=iqn.2000-05.com.3pardata:22110002ac000aba
TargetAddress=10.44.2.20:3260,211
I-: cmd=0x6 len=0
T-: cmd=0x26 len=0
postgres01#
Login session:
postgres01# iscontrol -v -n path1
port = 3260
tags = 256
maxluns = 0
iqn = iqn.2010-09.com.enovafinancial:01:nut.postgres01
maxConnections = 1
maxRecvDataSegmentLength = 65536
maxXmitDataSegmentLength = 65536
maxBurstLength = 131072
firstBurstLength = 65536
defaultTime2Wait = 0
defaultTime2Retain = 0
maxOutstandingR2T = 1
errorRecoveryLevel = 0
targetPortalGroupTag = 0
headerDigest = None,CRC32C
dataDigest = None,CRC32C
initialR2T = 1
immediateData = 1
dataPDUInOrder = 1
dataSequenceInOrder = 1
sessionType = Normal
targetAddress = 10.44.2.20
targetAlias = (null)
targetName = iqn.2000-05.com.3pardata:22110002ac000aba
initiatorName = iqn.2010-09.com.enovafinancial:01:nut.postgres01
initiatorAlias = (null)
authMethod = none
chapSecret = (null)
chapIName = (null)
tgtChapName = (null)
tgtChapSecret = (null)
tgttgtChallengeLen = 0
I-: cmd=0x3 len=433
SessionType=Normal
InitiatorName=iqn.2010-09.com.enovafinancial:01:nut.postgres01
TargetName=iqn.2000-05.com.3pardata:22110002ac000aba
MaxBurstLength=131072
HeaderDigest=None,CRC32C
DataDigest=None,CRC32C
MaxRecvDataSegmentLength=65536
ErrorRecoveryLevel=0
DefaultTime2Wait=0
DefaultTime2Retain=0
DataPDUInOrder=Yes
DataSequenceInOrder=Yes
MaxOutstandingR2T=1
MaxConnections=1
FirstBurstLength=65536
InitialR2T=Yes
ImmediateData=Yes
T-: cmd=0x23 len=267
MaxBurstLength=131072
HeaderDigest=None
DataDigest=None
MaxRecvDataSegmentLength=65536
ErrorRecoveryLevel=0
DefaultTime2Wait=2
Re: 3par iscsi with 8.2?
No, I`m not. But have some experience in iscsi. What kind of trouble do you have? -- View this message in context: http://freebsd.1045724.n5.nabble.com/3par-iscsi-with-8-2-tp4306095p4307912.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
3par iscsi with 8.2?
Is anyone connecting to 3par SAN units using iscsi with release 8.2? I am trying to do this, and having some trouble. -Derek ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 8.1 iSCSI CHAP with header and data digest
I am trying to connect my FreeBSD 8.1 system to a FreeNAS server
hosting an iSCSI drive. I can successfully connect if I disable header
and data digests, but can't seem to get a connection using header and
data digests to succeed. I know the FreeNAS side is correct because I
was able to connect and successfully format the drive and write data to
it using my Windows 7 PC with CHAP and digests enabled. Here is my
FreeBSD iscsi.conf file, do any of you have any idea what I am doing
wrong?
webmail# vim /etc/iscsi.conf
## Global Config
InitiatorName=ign.2005-01.il.ac.huji.cs:webmail.dweimer.local;
## Targets
# FreeNAS Backup Drive
backup {
TargetName=iqn.2007-09.jp.ne.peach.istgt:backup
TargetAddress=192.168.1.2
AuthMethod=CHAP
chapIName=webmail
chapSecret=Password1234
}
Also when I connect using the iscontrol -c /etc/iscsi.conf -n backup
command, I can't find a way to disconnect the drive. I ended up
rebooting the server to disconnect it so I could go back to testing with
digests enabled. Does anyone know how to disconnect an iscsi connection
once connected without rebooting?
--
Thanks,
Dean E. Weimer
http://www.dweimer.net/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD-8.1 on iscsi - Help Needed
I am trying to install FreeBSD-8.1 on a iscsi target disk but when I start installation it complains about No Hard disk found. I have iscsi enabled network adapter and I can configure the iscsi disk in the network adapter's iscsi ROM. When the system boots up from FreeBSD installation CD, I go to the command prompt and load if_em, iscsi_initiator and iscsi modules. I can run enable-module if_em command, but when I run enable-module iscsi_initiator it complains that iscsi_initiator not found. Has anyone installed FreeBSD on iscsi target? If so, what have you done so that during installation FreeBSD sees iscsi target as a disk on which to install the OS. Thanks Nihir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
zfs performance issues with iscsi (istgt)
After scratching my head for a few weeks, I've decided to ask for some help. First, I've got two machines connected by gigabit ethernet, network performance is not a problem as I am able to substantially saturate the wire when not using iscsi [say iperf] or ftp. Both systems are 8.1-RELENG. They are both multi-core, 8G of RAM. Symptoms: When doing writes (size relatively independent) from a client to a server via iSCSI I seem to be hitting a wall between 18-26MB/s of write. This can be repeated continuously whether doing a newfs on a 2TB iscsi volume or doing a dd from /dev/zero to the iscsi target. I haven't compared read performance. What originally put me on to this was watching the newfs *fly* across the screen, and then hang for several seconds, and then *fly* again, and then pause. This looked like a write-delay problem, so I tweaked txgwrite values and/or the synctime values. This showed some improvements (iostat showed something closer to continuous write performance to the server but there was still a delay whether the write_limit was 384MB all the way up to 4GB. This tells me the spindles weren't holding the throughput back. The iostat size was never much beyond 20-26MB/s, peaks were frequently two-three times that, but then it would be 1MB/s for a few seconds which would bring us back to this average). CPU and network load were never the limiting factor, nor did the spindles ever get above 20-30% busy. So I added two USB keys that write at around 30-40MB/s, and mirrored them as a ZIL log. iostat verifies they are being used, but not continuously, it seems that the txgwrite value applies to writing to the ZIL. I also tried turning off the ZIL log and saw no particular performance increase (or decrease). When newfs (which jumps around a lot more than dd) the performance throughput does not change much at all. Even at 26K-40K pps, interrupt loads and such are not problematic, turning on polling does not change the performance appreciably. The server is a RAIDZ2 of 15 drives @ 2TB each. So *write* throughput should be pretty fast sequentially (i.e. the dd case), but it is returning identically. This server does nothing much but istgt -- tried NCQ values from 255 down to 32 to no improvement. Even though network performance was not showing a particular limit, I *did* get from 18MB/s to 26MB/s by tweaking tcp sendbuf* and tcp send* values way beyond reason even though the TCP throughput hadn't been a problem in non iscsi operations. So whatever i'm doing is not addressing the particular problem. The drives have plenty of available I/O, but instead of using it, or the RAM in the system, or the ZIL in the system, it seems largely idle, pegs the system with continuous (but not max speed) writes and halts the network transfers, and then continues on its way. Even if its a threading issue (i.e. we are single threading) there should be some way to make this behave like a normal system considering how much RAM, SSD, and other resources I'm trying to through at this thing. For example, after the buffer starts to empty, additional writes from the client should be accepted and NCQ should help reorder to process them in an efficient fashion, etc, etc. istgt settings: istgt version 0.3 istgt extra version 20100707 MaxSessions 32 MaxConnections 32 FirstBurstLength 65536 MaxBurstLength 262144 MaxRecvDataSegmentLength 262144 Local benchmarks like dd if=/dev/zero of=/tank/dump bs=1M count=12000 returns like 200MB/s. 12582912000 bytes transferred in 61.140903 secs (205801867 bytes/sec), and show continuous (as expected) writes to the spindles. (200MB/s is pretty close to the max I/O speed we can expect given the port the controller is in and RAID overhead, etc with 7200 RPM drives, at 5900 RPM the number is about 80MB/s). If this is an istgt problem, is there a way to get reasonable performance out of it? I know I'm not losing my mind here, so if someone has tackled this particular problem (or its sort), please chime in and let me know what tunable I'm missing. :) Thanks very much, in advance, DJ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: zfs performance issues with iscsi (istgt)
On 08.11.2010 09:13, DJ wrote: After scratching my head for a few weeks, I've decided to ask for some help. First, I've got two machines connected by gigabit ethernet, network performance is not a problem as I am able to substantially saturate the wire when not using iscsi [say iperf] or ftp. Both systems are 8.1-RELENG. They are both multi-core, 8G of RAM. Symptoms: When doing writes (size relatively independent) from a client to a server via iSCSI I seem to be hitting a wall between 18-26MB/s of write. This can be repeated continuously whether doing a newfs on a 2TB iscsi volume or doing a dd from /dev/zero to the iscsi target. I haven't compared read performance. What originally put me on to this was watching the newfs *fly* across the screen, and then hang for several seconds, and then *fly* again, and then pause. I'll snip down this mail a little bit to ask some control questions (having recently had quite a wrestle with iSCSI myself). -Is jumbo frames involved? (and enabled on the initiator, all switches in between, and the target) -What's the number of PPS (some switches have PPS issues, which becomes painfully relevant for small block IO)? (I got rid of most of my problems when I replaced the Netgear GS724Tv3 switch with a Cisco SG-300) -Are you running digests? -Do you have TSO/TSOv2 enabled at the endpoints? -Does top -HSC reveal anything? -Does systat -vmstat 1 reveal anything? -What's the ICMP (ping) roundtrip times between the initiator and target IPs? //Svein -- +---+--- /\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE +---+--- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? Picture Gallery: https://gallery.stillbilde.net/v/svein/ signature.asc Description: OpenPGP digital signature
6.4 Netapp iscsi
Hello! I have to implement Bacula using NetApp iscsi. I have already searched for a while, but found only solutions for 7.x and higher or FreeBSD as a iscsi target. How can i do that on 6.4? Greetings Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD/iSCSI intiator into EMC Clarion target
uname -a FreeBSD xxx 7.1-RELEASE FreeBSD 7.1-RELEASE #0 kldstat Id Refs AddressSize Name 15 0xc040 97f830 kernel 21 0xc0d8 ff18 iscsi_initiator.ko 31 0xc0d9 6a2c4acpi.ko iscontrol doesn't have -V version and strings doesn't find anything that looks like a version. iscontrol -d -v -t 192.168.78.5 port = 3260 tags = 0 maxluns = 0 iqn = iqn.2005-01.il.ac.huji.cs: maxConnections = 1 maxRecvDataSegmentLength = 65536 maxXmitDataSegmentLength = 65536 maxBurstLength = 131072 firstBurstLength = 65536 defaultTime2Wait = 0 defaultTime2Retain = 0 maxOutstandingR2T = 1 errorRecoveryLevel = 0 targetPortalGroupTag = 0 headerDigest = None,CRC32C dataDigest = None,CRC32C initialR2T = 1 immediateData = 1 dataPDUInOrder = 1 dataSequenceInOrder = 1 sessionType = Normal targetAddress = (null) targetAlias = (null) targetName = (null) initiatorName = (null) initiatorAlias = (null) authMethod = None chapSecret = (null) chapIName = (null) tgtChapName = (null) tgtChapSecret = (null) tgttgtChallengeLen = 0 I-: cmd=0x3 len=301 SessionType=Discovery InitiatorName=iqn.2005-01.il.ac.huji.cs::mr1..net MaxBurstLength=131072 HeaderDigest=None,CRC32C DataDigest=None,CRC32C MaxRecvDataSegmentLength=65536 ErrorRecoveryLevel=0 DefaultTime2Wait=0 DefaultTime2Retain=0 DataPDUInOrder=Yes DataSequenceInOrder=Yes MaxOutstandingR2T=1 T-: cmd=0x23 len=281 TargetPortalGroupTag=0 TargetAlias=1576.b3 HeaderDigest=None DataDigest=None MaxRecvDataSegmentLength=65536 MaxBurstLength=Irrelevant DefaultTime2Wait=0 DefaultTime2Retain=0 MaxOutstandingR2T=Irrelevant DataPDUInOrder=Irrelevant DataSequenceInOrder=Irrelevant ErrorRecoveryLevel=0 I-: cmd=0x4 len=16 SendTargets=All recvpdu: Socket is not connected recvpdu failed I-: cmd=0x6 len=0 recvpdu: Socket is not connected recvpdu failed == iniatator does work into a FreeBSD/iscsi-target: # iscontrol -c /etc/iscsi.conf -n target0 iscontrol[817]: running iscontrol[817]: (pass3:iscsi0:0:0:0): tagged openings now 0 iscontrol[817]: cam_open_btl: no passthrough device found at 2:0:1 iscontrol[817]: cam_open_btl: no passthrough device found at 2:0:2 iscontrol[817]: cam_open_btl: no passthrough device found at 2:0:3 iscontrol: supervise starting main loop #ll /dev/is* crw--- 1 root wheel0, 27 Jul 8 13:29 /dev/iscsi crw--- 1 root wheel0, 103 Jul 8 13:29 /dev/iscsi0 #ll /dev/da* crw-r- 1 root operator0, 90 Jul 8 13:29 /dev/da0 crw-r- 1 root operator0, 91 Jul 8 13:29 /dev/da0s1 crw-r- 1 root operator0, 92 Jul 8 08:30 /dev/da0s1a crw-r- 1 root operator0, 93 Jul 8 13:30 /dev/da0s1b crw-r- 1 root operator0, 94 Jul 8 13:29 /dev/da0s1c crw-r- 1 root operator0, 95 Jul 8 08:29 /dev/da0s1d crw-r- 1 root operator0, 96 Jul 8 08:29 /dev/da0s1e crw-r- 1 root operator0, 105 Jul 8 13:29 /dev/da1 crw-r- 1 root operator0, 106 Jul 8 13:29 /dev/da1s1 crw-r- 1 root operator0, 107 Jul 8 13:29 /dev/da1s1c crw-r- 1 root operator0, 108 Jul 8 13:29 /dev/da1s1d #mount /dev/da1s1 /iscsitest/ #df Filesystem 1K-blocksUsedAvail Capacity Mounted on /dev/da0s1a 10154158 141662 9200164 2%/ devfs 1 10 100%/dev /dev/da0s1d 20308398 1393604 17290124 7%/usr /dev/da0s1e 40622090 292054 37080270 1%/var /dev/da1s19907690 2990276 612480033%/iscsitest = Red Hat Enterprise iscsi initiator connects to EMC SAN target reliably. If we can't get the FreeBSD iniatator working, we'll have to convert several machines from FreeBSD to Linux. Len ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
7.2-STABLE and iSCSI
Hello, I am currently using a 7.2-STABLE with iSCSI enabled in the kernel. I have tried to enable a file system which is 2.4TB in size (this is on an amd64 architecture). I have followed different documentations I found and can export an iSCSI target fine and initiate the iSCSI drive either on a Linux or FreeBSD client. I am using the /usr/ports/net/iscsi-target-20080207_2 The problem is concerning the size, as the maximum of the file system I see is 800G out of 2.4TB. I have double checked the target (server) and the initiator (client) and the cylinders is what does not match. On the server I have a slice with 15000 cylinders whereas the client sees only 4000 of them. All the other figures match. So, did I hit a limitation or am I just doing something wrong? Thanks for your help, Steph ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: iSCSI initiator lockups
--VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In our last exciting episode, Danny Braniss (da...@cs.huji.ac.il) said: I guess it's time to fix this. danny Thank you very much for the pointer to the newer version; we have seen a=20 marked improvement with none of the 30 second studdering. I appreciate your rapid assistance! Good, can you send me the info of the target/s you are using to add to the list of supported targets? Cheers, danny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: iSCSI initiator lockups
--ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm running into some odd headaches regarding what looks like iSCSI initiat= ors going to sleep for approximately 30 seconds before returning to life and pumping a ton of information back to the target. While this is happening, system load climbs up alarmingly fast. Looking at tcpdumps in Wireshark, it shows what appears to be a nearly exact 30 second delay where the initiator stops talking to the target server, then abruptly restarts. Currently 8 machines are talking to 2 servers with 4 targets a piece, and while its= =20 working, we get good throughput. Activity is moderately high, as we are=20 using the iSCSI targets as spool disks in an email cluster. As it appears that iscsi-target is a single-threaded process, would it be valuable to put each target in its own process on its own port? At any rate, this is causing serious problems on the mail processing machines. can you send me the output of sysctl net.iscsi chears, danny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
iSCSI initiator lockups
I'm running into some odd headaches regarding what looks like iSCSI initiators going to sleep for approximately 30 seconds before returning to life and pumping a ton of information back to the target. While this is happening, system load climbs up alarmingly fast. Looking at tcpdumps in Wireshark, it shows what appears to be a nearly exact 30 second delay where the initiator stops talking to the target server, then abruptly restarts. Currently 8 machines are talking to 2 servers with 4 targets a piece, and while its working, we get good throughput. Activity is moderately high, as we are using the iSCSI targets as spool disks in an email cluster. As it appears that iscsi-target is a single-threaded process, would it be valuable to put each target in its own process on its own port? At any rate, this is causing serious problems on the mail processing machines. -- Jason T. Nelson j...@jtn.cx GPG key 0xFF676C9E pgpAAGlC6hiog.pgp Description: PGP signature
FreeBSD + Samba + OpenLDAP + iSCSI +Netapp , anyone ?
Hello All is in the subject :-) Does anyone has setup such server configuration A server running FreeBSD and supporting Samba server software with OpenLDAP backend and using iSCSI as disk access protocol to a Netapp filer for Samba volumes ? I plan this so passed experiences are welcome ! Thanks a lot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD + Samba + OpenLDAP + iSCSI +Netapp , anyone ?
On Fri, Mar 6, 2009 at 1:37 AM, Frank Bonnet f.bon...@esiee.fr wrote: Hello All is in the subject :-) Does anyone has setup such server configuration A server running FreeBSD and supporting Samba server software with OpenLDAP backend and using iSCSI as disk access protocol to a Netapp filer for Samba volumes ? I plan this so passed experiences are welcome ! Thanks a lot I've done the Samba+OpenLDAP -- I have an install still running off that. iSCSI isn't hard to add into it, but I've never heard or ran Netapp. So I'd offer my help with OpenLDAP+Samba. iSCSI is easy (keeping in mind the ACL built into iSCSI); and maybe someone else can help with Netapp. Good Luck. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Tool for benchmark local disk vs. iSCSI
Hi, To gain an understanding on the performance of iSCSI vs. local disk IO I'm looking for a tool. My first thought was about iozone... Any other ideas? Thanks much in advance for your help, -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tool for benchmark local disk vs. iSCSI
To gain an understanding on the performance of iSCSI vs. local disk IO I'm looking for a tool. My first thought was about iozone... Any other ideas? for linear transfer:dd of course iSCSI disk will always be slower ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tool for benchmark local disk vs. iSCSI
Ewald Jenisch wrote: Hi, To gain an understanding on the performance of iSCSI vs. local disk IO I'm looking for a tool. My first thought was about iozone... iozone is ok, but a little complex to run. Any disk benchmark will be ok - bonnie++, blogbench, etc. but each has an emphasis on a different aspect of the system. I think bonnie++ will be the simplest in your case. Make sure you know what you're benchmarking - for example if the iSCSI drive (target) is hosted as a file in a regular file system, it will be overly (and dangerously) cached on the server. signature.asc Description: OpenPGP digital signature
Re: Tool for benchmark local disk vs. iSCSI
Ewald Jenisch wrote: Hi, To gain an understanding on the performance of iSCSI vs. local disk IO I'm looking for a tool. My first thought was about iozone... bonnie++ is ok too. Any other ideas? Thanks much in advance for your help, -ewald ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tool for benchmark local disk vs. iSCSI
My first thought was about iozone... iozone is ok, but a little complex to run. Any disk benchmark will be ok - bonnie++, blogbench, etc. but each has an emphasis on a different aspect of the system. I think bonnie++ will be the simplest in your case. can bonnie++ operate on raw device not filesystem? he asked about disk benchmarked not disk+filesystem Make sure you know what you're benchmarking - for example if the iSCSI drive (target) is hosted as a file in a regular file system, it will be overly (and dangerously) cached on the server. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Tool for benchmark local disk vs. iSCSI
Wojciech Puchar wrote: My first thought was about iozone... iozone is ok, but a little complex to run. Any disk benchmark will be ok - bonnie++, blogbench, etc. but each has an emphasis on a different aspect of the system. I think bonnie++ will be the simplest in your case. can bonnie++ operate on raw device not filesystem? he asked about disk benchmarked not disk+filesystem Sorry, you're right. signature.asc Description: OpenPGP digital signature
Re: ZFS over iSCSI anyone ?
Ivan Voras wrote: Jeremy Chadwick wrote: On Mon, Nov 17, 2008 at 04:29:06PM +0100, Ivan Voras wrote: Jeremy Chadwick wrote: On Mon, Nov 17, 2008 at 03:44:23PM +0100, Frank Bonnet wrote: Hello Does anyone has tried to use ZFS over iSCSI ? Another FreeBSD user recently brought to my attention problems with iSCSI on FreeBSD. There is a patch available which fixes the issue, but I felt you might want to know about it beforehand. Issue: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003383.html Patch: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003387.html Isn't this committed already? The user tells me it is not, and that his replies to the patch author have gone ignored. It looks like the iSCSI developer disappeared - I got a bounce message (in French) on the last e-mail :( It looks like there's new development in -CURRENT: http://svn.freebsd.org/viewvc/base?view=revisionrevision=185289 signature.asc Description: OpenPGP digital signature
Re: ZFS over iSCSI anyone ?
Ivan Voras wrote: Ivan Voras wrote: Jeremy Chadwick wrote: On Mon, Nov 17, 2008 at 04:29:06PM +0100, Ivan Voras wrote: Jeremy Chadwick wrote: On Mon, Nov 17, 2008 at 03:44:23PM +0100, Frank Bonnet wrote: Hello Does anyone has tried to use ZFS over iSCSI ? Another FreeBSD user recently brought to my attention problems with iSCSI on FreeBSD. There is a patch available which fixes the issue, but I felt you might want to know about it beforehand. Issue: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003383.html Patch: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003387.html Isn't this committed already? The user tells me it is not, and that his replies to the patch author have gone ignored. It looks like the iSCSI developer disappeared - I got a bounce message (in French) on the last e-mail :( It looks like there's new development in -CURRENT: http://svn.freebsd.org/viewvc/base?view=revisionrevision=185289 Well good news ! it seems to be integrated inside operating system isn't it ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ZFS over iSCSI anyone ?
2008/11/26 Frank Bonnet [EMAIL PROTECTED]: Well good news ! it seems to be integrated inside operating system isn't it ? Yes, the patch is for -CURRENT (which means it will be present in the 8.0 release; bug the developers if you need it earlier). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
ZFS over iSCSI anyone ?
Hello Does anyone has tried to use ZFS over iSCSI ? Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ZFS over iSCSI anyone ?
On Mon, Nov 17, 2008 at 03:44:23PM +0100, Frank Bonnet wrote: Hello Does anyone has tried to use ZFS over iSCSI ? Another FreeBSD user recently brought to my attention problems with iSCSI on FreeBSD. There is a patch available which fixes the issue, but I felt you might want to know about it beforehand. Issue: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003383.html Patch: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003387.html -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ZFS over iSCSI anyone ?
Jeremy Chadwick wrote: On Mon, Nov 17, 2008 at 03:44:23PM +0100, Frank Bonnet wrote: Hello Does anyone has tried to use ZFS over iSCSI ? Another FreeBSD user recently brought to my attention problems with iSCSI on FreeBSD. There is a patch available which fixes the issue, but I felt you might want to know about it beforehand. Issue: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003383.html Patch: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003387.html Thanks a lot for you quick answer ! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ZFS over iSCSI anyone ?
Jeremy Chadwick wrote: On Mon, Nov 17, 2008 at 03:44:23PM +0100, Frank Bonnet wrote: Hello Does anyone has tried to use ZFS over iSCSI ? Another FreeBSD user recently brought to my attention problems with iSCSI on FreeBSD. There is a patch available which fixes the issue, but I felt you might want to know about it beforehand. Issue: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003383.html Patch: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003387.html Isn't this committed already? signature.asc Description: OpenPGP digital signature
Re: ZFS over iSCSI anyone ?
On Mon, Nov 17, 2008 at 04:29:06PM +0100, Ivan Voras wrote: Jeremy Chadwick wrote: On Mon, Nov 17, 2008 at 03:44:23PM +0100, Frank Bonnet wrote: Hello Does anyone has tried to use ZFS over iSCSI ? Another FreeBSD user recently brought to my attention problems with iSCSI on FreeBSD. There is a patch available which fixes the issue, but I felt you might want to know about it beforehand. Issue: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003383.html Patch: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003387.html Isn't this committed already? The user tells me it is not, and that his replies to the patch author have gone ignored. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ZFS over iSCSI anyone ?
Jeremy Chadwick wrote: On Mon, Nov 17, 2008 at 04:29:06PM +0100, Ivan Voras wrote: Jeremy Chadwick wrote: On Mon, Nov 17, 2008 at 03:44:23PM +0100, Frank Bonnet wrote: Hello Does anyone has tried to use ZFS over iSCSI ? Another FreeBSD user recently brought to my attention problems with iSCSI on FreeBSD. There is a patch available which fixes the issue, but I felt you might want to know about it beforehand. Issue: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003383.html Patch: http://lists.freebsd.org/pipermail/freebsd-scsi/2008-February/003387.html Isn't this committed already? The user tells me it is not, and that his replies to the patch author have gone ignored. It looks like the iSCSI developer disappeared - I got a bounce message (in French) on the last e-mail :( signature.asc Description: OpenPGP digital signature
iSCSI support
Hi, My company is a storage RAID system company. There is one customer ask iSCSI solution with my production of my company with FreeBSD 6.1. But I found some information in the Internet, the iSCSI full support on FreeBSD is 7.0. Is it mean FreeBSD 6.1 can’t support iSCSI? BR, Jeff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI support
Jeff Chen - PTT 陳龍焜 wrote: Hi, My company is a storage RAID system company. There is one customer ask iSCSI solution with my production of my company with FreeBSD 6.1. But I found some information in the Internet, the iSCSI full support on FreeBSD is 7.0. Is it mean FreeBSD 6.1 can’t support iSCSI? Yes, the iSCSI initiator is in FreeBSD 7.x. Soon, FreeBSD 7.1 will be released. signature.asc Description: OpenPGP digital signature
Re: iSCSI support
can't be iSCSI client, but iscsi-target is userlevel app, you may run on any FreeBSD (most probably under any unix). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI support
Jeff Chen - PTT 陳龍焜 wrote: Hi, My company is a storage RAID system company. There is one customer ask iSCSI solution with my production of my company with FreeBSD 6.1. But I found some information in the Internet, the iSCSI full support on FreeBSD is 7.0. Is it mean FreeBSD 6.1 can’t support iSCSI? BR, Jeff ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] There are some patches around to run it on 6.2 (maybe all of 6.x) but the performance isn't very good. I used this on 6.2 and it did work: ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.0.92.tar.gz This looks like a more recent version (tho no guarantee it will work on 6.x): ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.1.tar.gz ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: open-iscsi ?
Frank Bonnet wrote: Hello Does open-iscsi has been ported to FreeBSD at 7.x ? it doesn't seems to be at 6.x Seems to be a linux specific implementation of iscsi and gnu licenced so no we dont. However we have iscsi_initiator(4) in 7.x see the man pages for details. For a iscsi target daemon see net/iscsi-target in ports. Vince thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: open-iscsi ?
Vincent Hoffman wrote: Frank Bonnet wrote: Hello Does open-iscsi has been ported to FreeBSD at 7.x ? it doesn't seems to be at 6.x Seems to be a linux specific implementation of iscsi and gnu licenced so no we dont. However we have iscsi_initiator(4) in 7.x see the man pages for details. For a iscsi target daemon see net/iscsi-target in ports. Vince Thanks I'm gonna check those ports. Frank ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
open-iscsi ?
Hello Does open-iscsi has been ported to FreeBSD at 7.x ? it doesn't seems to be at 6.x thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD and ISCSI, Strange Problem
I'm with a very strange problem in the FreeBSD 7.0R I use the iscsi_initiator to mount two devices of a Dell MD3000i, the file system is UFS. The problem occurs when I make a copy of a great directory for inside of the /data/email directory, passed some minutes of beginning of copy, the SSH connection stops to answer, when trying to open a new connection Password: it isn't requested, in the console, when typing the user root e to press enter, Password: also it isn't requested. The only way to come back is restarting the FreeBSD. When press CTRL+T during the freeze it is shown: # ssh [EMAIL PROTECTED] load: 0.76 cmd: ssh 86930 [sbwait] 0.00u 0.01s 0% 2076k In another freeze it showed state [ufs] During freeze, send and receive pings work fine, but no service runing work. I already verified for some related LOG, however not see nothing related. MOUNT: /dev/da0s1g on /home (ufs, local, soft-updates) /dev/da0s1f on /tmp (ufs, local, soft-updates) /dev/da0s1d on /usr (ufs, local, soft-updates) /dev/da0s1e on /var (ufs, NFS exported, local, soft-updates) /dev/da2s1d on /data/db (ufs, NFS exported, local, soft-updates) /dev/da3s1d on /data/email (ufs, NFS exported, local, soft-updates) DMESG: Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-RELEASE #0: Mon Sep 15 20:00:35 BRT 2008 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz (2329.84-MHz 686-class CPU) Origin = GenuineIntel Id = 0x10676 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xce3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,b19 AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 4 real memory = 3484745728 (3323 MB) avail memory = 3405615104 (3247 MB) ACPI APIC Table: DELL PE_SC3 FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0: Changing APIC ID to 4 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) hptrr: HPT RocketRAID controller driver v1.1 (Sep 15 2008 20:00:23) acpi0: DELL PE_SC3 on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 acpi_hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff on acpi0 Timecounter HPET frequency 14318180 Hz quality 900 cpu0: ACPI CPU on acpi0 est0: Enhanced SpeedStep Frequency Control on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 720072006000720 device_attach: est0 attach returned 6 p4tcc0: CPU Frequency Thermal Control on cpu0 cpu1: ACPI CPU on acpi0 est1: Enhanced SpeedStep Frequency Control on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 720072006000720 device_attach: est1 attach returned 6 p4tcc1: CPU Frequency Thermal Control on cpu1 cpu2: ACPI CPU on acpi0 est2: Enhanced SpeedStep Frequency Control on cpu2 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 720072006000720 device_attach: est2 attach returned 6 p4tcc2: CPU Frequency Thermal Control on cpu2 cpu3: ACPI CPU on acpi0 est3: Enhanced SpeedStep Frequency Control on cpu3 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 720072006000720 device_attach: est3 attach returned 6 p4tcc3: CPU Frequency Thermal Control on cpu3 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci4: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci4 pci5: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge at device 0.0 on pci5 pci6: ACPI PCI bus on pcib3 pcib4: PCI-PCI bridge at device 0.0 on pci6 pci7: PCI bus on pcib4 bce0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) mem 0xf400-0xf5ff irq 16 at device 0.0 on pci7 miibus0: MII bus on bce0 brgphy0: BCM5708C 10/100/1000baseTX PHY PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto bce0: Ethernet address: 00:1e:c9:b4:e5:2b bce0: [ITHREAD] bce0: ASIC (0x57081020); Rev (B2); Bus (PCI-X, 64-bit, 133MHz); F/W (0x04000305); Flags( MFW MSI ) pcib5: ACPI PCI-PCI bridge at device 1.0 on pci5 pci8: ACPI PCI bus on pcib5 pcib6: PCI-PCI bridge at device 0.3 on pci4 pci9: PCI bus on pcib6 pcib7: ACPI PCI-PCI bridge at device 3.0 on pci0 pci1: ACPI PCI bus on
iscsi multiple sessions per target support
Hi, I'm using FreeBSD 7.0 RELEASE on amd64 and want to connect to an iSCSI storage array that has dual SAN controllers. I have two independent paths between my FreeBSD box and the storage array -- dual NICs, ethernet switches, and controllers. Given my situation, I want to ensure I get better performance and failover by using both my paths to the iSCSI target. I can't seem to find this covered in any of the man pages or the handbook. My storage array supports multiple sessions per target. Does the iSCSI initiator in 7.0 RELEASE support this feature? If supported, how does one go about configuring it? I'm sorry if this question is already covered in the literature. Thanks in advance for any help! - Raja ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI initiator
Please clarify these : (1) Is iSCSI initiator not currently implemented for FreeBSD ? no idea. (2) There is no iSCSI target daemon currently ? /usr/ports/net/iscsi-target unless you HAVE to interwork with iSCSI, use ggate. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: iSCSI initiator
Please clarify these : (1) Is iSCSI initiator not currently implemented for FreeBSD ? (2) There is no iSCSI target daemon currently ? Check this post, it has step by step instructions for 6.x: http://www.southernledger.com/blogs/ee99ee/?p=33 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
iSCSI initiator
Please clarify these : (1) Is iSCSI initiator not currently implemented for FreeBSD ? (2) There is no iSCSI target daemon currently ? Regards, Onkar ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI initiator
* Onkar [EMAIL PROTECTED] [05-16-2008]: (1) Is iSCSI initiator not currently implemented for FreeBSD ? http://www.freebsd.org/releases/7.0R/announce.html (2) There is no iSCSI target daemon currently ? net/iscsi-target -- Sahil Tandon [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI initiator
Sahil Tandon wrote: * Onkar [EMAIL PROTECTED] [05-16-2008]: (1) Is iSCSI initiator not currently implemented for FreeBSD ? http://www.freebsd.org/releases/7.0R/announce.html (2) There is no iSCSI target daemon currently ? net/iscsi-target Onkar, you may also find this helpful. http://conshell.net/wiki/index.php/User:Fostermarkd/FreeBSD/iSCSI -- Said one park ranger, 'There is considerable overlap between the intelligence of the smartest bears and the dumbest tourists.' Mark D. Foster, CISSP [EMAIL PROTECTED] http://mark.foster.cc/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
iSCSI and multi-terabyte support?
At my place of work, we're looking at implementing a SAN, most likely with iSCSI, some time next year, and likely about 5-10TBytes. I was wondering if FreeBSD could provide this on COTS hardware, but my googling hasn't been successful. From my reading of this list over the past couple of years, it seems that both parts of the solution - iSCSI support and large disk support - are still problematic, but I'd like to hear more informed opinion, as the potential cost savings is quite large. Anyone have recent-ish experience putting something like this together? Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI and multi-terabyte support?
On 10/10/07, Kurt Buff [EMAIL PROTECTED] wrote: At my place of work, we're looking at implementing a SAN, most likely with iSCSI, some time next year, and likely about 5-10TBytes. I was wondering if FreeBSD could provide this on COTS hardware, but my googling hasn't been successful. From my reading of this list over the past couple of years, it seems that both parts of the solution - iSCSI support and large disk support - are still problematic, but I'd like to hear more informed opinion, as the potential cost savings is quite large. Anyone have recent-ish experience putting something like this together? IMHO opinion I do not think FreeBSD is there...yet. ZFS is addressing many of the enterprise filesystem features that would be needed to implement something on this scale, and there is the iSCSI target from NetBSD available in the ports tree. I think 7-RELEASE is going to be a solid foundation for building solutions like this - but in the mean time it may be worth considering OpenSolaris if are considering going the COTS path. or - you can take a look at a company like Isilon Systems (http://www.isilon.com/) which builds very scalable filers based on FreeBSD. I have beta tested their iSCSI implementation and it does look good. HTH -pete -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI and multi-terabyte support?
On 10/10/07, pete wright [EMAIL PROTECTED] wrote: On 10/10/07, Kurt Buff [EMAIL PROTECTED] wrote: At my place of work, we're looking at implementing a SAN, most likely with iSCSI, some time next year, and likely about 5-10TBytes. I was wondering if FreeBSD could provide this on COTS hardware, but my googling hasn't been successful. From my reading of this list over the past couple of years, it seems that both parts of the solution - iSCSI support and large disk support - are still problematic, but I'd like to hear more informed opinion, as the potential cost savings is quite large. Anyone have recent-ish experience putting something like this together? IMHO opinion I do not think FreeBSD is there...yet. ZFS is addressing many of the enterprise filesystem features that would be needed to implement something on this scale, and there is the iSCSI target from NetBSD available in the ports tree. I think 7-RELEASE is going to be a solid foundation for building solutions like this - but in the mean time it may be worth considering OpenSolaris if are considering going the COTS path. or - you can take a look at a company like Isilon Systems (http://www.isilon.com/) which builds very scalable filers based on FreeBSD. I have beta tested their iSCSI implementation and it does look good. HTH -pete Thanks - being a noob at this particular part of IT, I appreciate the feedback. Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
iSCSI hardware HBA status
hi all, i have tried googling for the current status of iSCSI software and hardware HBA support in FreeBSD. A lot of the hit's seem pretty stale. Is there active development going on with support hardware iSCSI HBA's in current by any chance? I have not been able to find any listed cards. For example I have a Qlogic 1gig 2port HBA with a ISP4022 chipset. Is any work being done on this? I would be willing to do some testing if time permits on my end. thanks! -pete -- ~~o0OO0o~~ Pete Wright www.nycbug.org NYC's *BSD User Group ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI
John Nielsen wrote: On Monday 08 January 2007 14:52, DAve wrote: We are moving to SAN in the near future to resolve a host of issues. I have been looking through archives for information on FreeBSD and iSCSI without much success. We currently have 15 servers running FreeBSD and several more in the queue/on order. It is looking like FreeBSD may not provide the production level of iSCSI initiator we will require. (The iSCSI target host will be a third party vendor) I am sending a request for information to the project lead but I am also interested in knowing if anyone is currently using any iSCSI with FreeBSD and what your success failures might be. I just started using the latest iSCSI initiator[1] on my 6-STABLE desktop to access some volumes on a LeftHand Networks SAN. It's a bit lacking in polish, but it works quite well. The one big missing feature is that it doesn't handle network disconnections. No panics or anything though, and performance was what I expected. I'd be interested in what Danny tells you about the initiator's readiness for production use, but in any case you'll probably just have to do some stability and stress testing on your own. [1] ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-17.5.tar.bz2 JN The developers response, for those who are interested. hi Dave, the initiator for iSCSI will hit stable/current real soon now. that was the good news, now for the down side: what was missing all along was recovery from network disconnects, so while I think I have it almost worked out, I've come across a major flow in the iscsi design: when the targets crashes, and comes back, there is no way to tell the client to run an fsck. This is not a problem if the client is mounting the iscsi partition read only. danny Thanks everyone who responded on and off list to me. DAve -- Three years now I've asked Google why they don't have a logo change for Memorial Day. Why do they choose to do logos for other non-international holidays, but nothing for Veterans? Maybe they forgot who made that choice possible. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI
In the last episode (Jan 09), DAve said: The developers response, for those who are interested. hi Dave, the initiator for iSCSI will hit stable/current real soon now. that was the good news, now for the down side: what was missing all along was recovery from network disconnects, so while I think I have it almost worked out, I've come across a major flow in the iscsi design: when the targets crashes, and comes back, there is no way to tell the client to run an fsck. This is not a problem if the client is mounting the iscsi partition read only. danny Why should the client need to do an fsck? From its point of view it should just look like the target had the iSCSI equivalent of a bus reset. It should resend any queued requests and continue. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI
Dan Nelson wrote: In the last episode (Jan 09), DAve said: The developers response, for those who are interested. hi Dave, the initiator for iSCSI will hit stable/current real soon now. that was the good news, now for the down side: what was missing all along was recovery from network disconnects, so while I think I have it almost worked out, I've come across a major flow in the iscsi design: when the targets crashes, and comes back, there is no way to tell the client to run an fsck. This is not a problem if the client is mounting the iscsi partition read only. danny Why should the client need to do an fsck? From its point of view it should just look like the target had the iSCSI equivalent of a bus reset. It should resend any queued requests and continue. That was my thought as well. I have my pop toasters all mounting a NFS mail store and when NFS goes away I don't have my NFS clients doing a fsck when the mount returns. Not sure if that is important as iSCSI is all new to me, still reading up on it. Does FreeBSD do anything special to a NFS mount when it returns? Should I subscribe to the SCSI list to continue this thread? DAve -- Three years now I've asked Google why they don't have a logo change for Memorial Day. Why do they choose to do logos for other non-international holidays, but nothing for Veterans? Maybe they forgot who made that choice possible. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI
That only works if the target comes up within the 2min window that SCSI allows for. It won't wait forever. On 1/9/07, Dan Nelson [EMAIL PROTECTED] wrote: In the last episode (Jan 09), DAve said: The developers response, for those who are interested. hi Dave, the initiator for iSCSI will hit stable/current real soon now. that was the good news, now for the down side: what was missing all along was recovery from network disconnects, so while I think I have it almost worked out, I've come across a major flow in the iscsi design: when the targets crashes, and comes back, there is no way to tell the client to run an fsck. This is not a problem if the client is mounting the iscsi partition read only. danny Why should the client need to do an fsck? From its point of view it should just look like the target had the iSCSI equivalent of a bus reset. It should resend any queued requests and continue. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Tuesday, January 09, 2007 12:14:15 -0500 DAve [EMAIL PROTECTED] wrote: That was my thought as well. I have my pop toasters all mounting a NFS mail store and when NFS goes away I don't have my NFS clients doing a fsck when the mount returns. Not sure if that is important as iSCSI is all new to me, still reading up on it. Does FreeBSD do anything special to a NFS mount when it returns? 'k, maybe I'm misunderstanding things, but iSCSI != NFS ... iSCSI is just removing your SCSI drives from your local server and putting them in a different location (over an ethernet connection) ... with NFS, you have one server to which multiple clients can connect ... with iSCSI, you have a one-to-one mapping of a file system on the 'target' to the server in question ... so, again, it was my understanding that stuff like an fsck is the responsibility of the server, not the target, same as if the SCSI drives were local to the server ... - Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFpDvG4QvfyHIvDvMRAhLCAKDXPvQB2ZVn3oZ42wt7su+nKmLrVgCgpyy2 UIyUtRnJy52ftxXgdoAKGT0= =AR/j -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI
Marc G. Fournier wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - --On Tuesday, January 09, 2007 12:14:15 -0500 DAve [EMAIL PROTECTED] wrote: That was my thought as well. I have my pop toasters all mounting a NFS mail store and when NFS goes away I don't have my NFS clients doing a fsck when the mount returns. Not sure if that is important as iSCSI is all new to me, still reading up on it. Does FreeBSD do anything special to a NFS mount when it returns? 'k, maybe I'm misunderstanding things, but iSCSI != NFS I never said it was, my rather poor example (I said I was new to iSCSI) was if a remote file system crashes, who should fsck it? The server (Target) or the client (Initiator)? ... iSCSI is just removing your SCSI drives from your local server and putting them in a different location (over an ethernet connection) ... with NFS, you have one server to which multiple clients can connect ... with iSCSI, you have a one-to-one mapping of a file system on the 'target' to the server in question ... so, again, it was my understanding that stuff like an fsck is the responsibility of the server, not the target, same as if the SCSI drives were local to the server ... As I thought. However, I clearly don't know much about iSCSI, though I know more with every page I read. I will always defer to those with experience, which is why I ask (sometimes stupid) questions ;^) DAve -- Three years now I've asked Google why they don't have a logo change for Memorial Day. Why do they choose to do logos for other non-international holidays, but nothing for Veterans? Maybe they forgot who made that choice possible. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI
I never said it was, my rather poor example (I said I was new to iSCSI) was if a remote file system crashes, who should fsck it? The server (Target) or the client (Initiator)? --- Clearly, the initiator. It owns the filesystem. Its just a big anonymous file on the target with no relevant structure that it cares about. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
iSCSI
We are moving to SAN in the near future to resolve a host of issues. I have been looking through archives for information on FreeBSD and iSCSI without much success. We currently have 15 servers running FreeBSD and several more in the queue/on order. It is looking like FreeBSD may not provide the production level of iSCSI initiator we will require. (The iSCSI target host will be a third party vendor) I am sending a request for information to the project lead but I am also interested in knowing if anyone is currently using any iSCSI with FreeBSD and what your success failures might be. Thank you, DAve -- Three years now I've asked Google why they don't have a logo change for Memorial Day. Why do they choose to do logos for other non-international holidays, but nothing for Veterans? Maybe they forgot who made that choice possible. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI
On Monday 08 January 2007 14:52, DAve wrote: We are moving to SAN in the near future to resolve a host of issues. I have been looking through archives for information on FreeBSD and iSCSI without much success. We currently have 15 servers running FreeBSD and several more in the queue/on order. It is looking like FreeBSD may not provide the production level of iSCSI initiator we will require. (The iSCSI target host will be a third party vendor) I am sending a request for information to the project lead but I am also interested in knowing if anyone is currently using any iSCSI with FreeBSD and what your success failures might be. I just started using the latest iSCSI initiator[1] on my 6-STABLE desktop to access some volumes on a LeftHand Networks SAN. It's a bit lacking in polish, but it works quite well. The one big missing feature is that it doesn't handle network disconnections. No panics or anything though, and performance was what I expected. I'd be interested in what Danny tells you about the initiator's readiness for production use, but in any case you'll probably just have to do some stability and stress testing on your own. [1] ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-17.5.tar.bz2 JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI
On Mon, 08 Jan 2007 14:52:06 -0500 DAve wrote: We are moving to SAN in the near future to resolve a host of issues. I have been looking through archives for information on FreeBSD and iSCSI without much success. We currently have 15 servers running FreeBSD and several more in the queue/on order. It is looking like FreeBSD may not provide the production level of iSCSI initiator we will require. (The iSCSI target host will be a third party vendor) I didn't use them myself but I'll second for hearing about them: http://ixsystems.com/storageiSCSI.php I am sending a request for information to the project lead but I am also interested in knowing if anyone is currently using any iSCSI with FreeBSD and what your success failures might be. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI
John Nielsen wrote: On Monday 08 January 2007 14:52, DAve wrote: We are moving to SAN in the near future to resolve a host of issues. I have been looking through archives for information on FreeBSD and iSCSI without much success. We currently have 15 servers running FreeBSD and several more in the queue/on order. It is looking like FreeBSD may not provide the production level of iSCSI initiator we will require. (The iSCSI target host will be a third party vendor) I am sending a request for information to the project lead but I am also interested in knowing if anyone is currently using any iSCSI with FreeBSD and what your success failures might be. I just started using the latest iSCSI initiator[1] on my 6-STABLE desktop to access some volumes on a LeftHand Networks SAN. It's a bit lacking in polish, but it works quite well. The one big missing feature is that it doesn't handle network disconnections. No panics or anything though, and performance was what I expected. I'd be interested in what Danny tells you about the initiator's readiness for production use, but in any case you'll probably just have to do some stability and stress testing on your own. [1] ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-17.5.tar.bz2 JN Thanks for the feedback. DAve -- Three years now I've asked Google why they don't have a logo change for Memorial Day. Why do they choose to do logos for other non-international holidays, but nothing for Veterans? Maybe they forgot who made that choice possible. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI
Boris Samorodov wrote: On Mon, 08 Jan 2007 14:52:06 -0500 DAve wrote: We are moving to SAN in the near future to resolve a host of issues. I have been looking through archives for information on FreeBSD and iSCSI without much success. We currently have 15 servers running FreeBSD and several more in the queue/on order. It is looking like FreeBSD may not provide the production level of iSCSI initiator we will require. (The iSCSI target host will be a third party vendor) I didn't use them myself but I'll second for hearing about them: http://ixsystems.com/storageiSCSI.php I am sending a request for information to the project lead but I am also interested in knowing if anyone is currently using any iSCSI with FreeBSD and what your success failures might be. WBR iSCSI Target and iSCSI initiator are two different animals. The above is for hosting a iSCSI system, providing a target(I believe), we need to connect to it, using an initiator. Thanks, DAve -- Three years now I've asked Google why they don't have a logo change for Memorial Day. Why do they choose to do logos for other non-international holidays, but nothing for Veterans? Maybe they forgot who made that choice possible. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI setup
I got bored, installed this on 5.3 with a Netapp F880. Slow isnt the word..anyone else try this with similar results? Like..max write speed is 600k/sec. On 10/23/06, freebsd [EMAIL PROTECTED] wrote: Hi, I'm trying to have my mailboxes put on iSCSI (NetAPP). I downloaded iscsi-17.5.tar.bz2 and have several questions: 1) is there some more documentation on this driver? 2) someone has pointed out how to specify user and password to pass to iscontrol? 3) Which is the correct way to put that source in the kernel and have it compiled? What I need to add to my kernel config file? Is there an howto specifying how to reach the final result of having my FreeBSD boot and mount then iSCSI drive to /iSCSI/myvolume? Thanks a lot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
iSCSI setup
Hi, I'm trying to have my mailboxes put on iSCSI (NetAPP). I downloaded iscsi-17.5.tar.bz2 and have several questions: 1) is there some more documentation on this driver? 2) someone has pointed out how to specify user and password to pass to iscontrol? 3) Which is the correct way to put that source in the kernel and have it compiled? What I need to add to my kernel config file? Is there an howto specifying how to reach the final result of having my FreeBSD boot and mount then iSCSI drive to /iSCSI/myvolume? Thanks a lot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
iSCSI support..
Freebsd ever hope to have a stable supported iscsi layer? Thanks for any hints. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI support..
On Thu, Oct 12, 2006 at 08:37:27PM -0700, Jeff Mohler wrote: Freebsd ever hope to have a stable supported iscsi layer? Thanks for any hints. I plan to starting testing FreeBSD 6.2 (when it is released) and iSCSI within the next few weeks. We have seattled on an HP DL360 with a Broadcom NIC talking to a NetApp. This will be our first pass at iSCSI. Should be intresting. Josef -- Josef Grosch | Another day closer to a | FreeBSD 6.1 [EMAIL PROTECTED] | Micro$oft free world | Berkeley, Ca. pgpLRYeJnNfV8.pgp Description: PGP signature
Freebsd as iscsi / aoe target (server)
Hi there,
can FreeBSD be used as an iSCSI target (i.e., serving the iscsi disks) ?
idem AoE ...?
thanks!
B
_
{Beto|Norberto|Numard} Meijome
He loves nature in spite of what it did to him.
Forrest Tucker
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI support
[EMAIL PROTECTED] wrote: I have 3 datacentres connected by 12 core gig fibre (only using one pair at the moment, but the fibre is there for future use) each connected directly to the others. I want a system that I can start off with one disk server in one datacentre, and then step it up to have mirrored disk servers in each of the other datacentre's which are kept up to date in real time and can take over instantaneously if one of the others fails. It must also be scalable (non destructive resizing of the system) and support both linux and FreeBSD. I am willing to wait for this, but can anyone point me in the right direction. iSCSI seems to be it, but I'm not sure. all, don't get network attached storage confused with network attached filesystem confused with clustered filesystem. if you go for fibre channel network attached storage, it dosen't matter if the host and storage array are in the same cabinet, across the room or in different data centers. if your requirement is only to have one host up at any time then it can raid1 3way mirror over the sites. of course it gets really messy when one of the links goes down and you have to decide if it really has and not just the way your testing, who becomes master and enforce it so there's no corruption (if the down host continues writing). you mention multiple cores and the datacenters connectected in a ring, which means you can multipath in both directions of the loop. don't know of any fc multipathing for freebsd. doing this in iscsi will be a lot cheaper. switches will be gigE with fibre uplinks to connect the sites. targets and initiators can be regular boxes with more/less/none directly attached disks, all connected via gig nics. multipathing/link failures are handled by routing daemons/protocols which already exist. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI support
from people. ICBW but to me it seems that iSCSI is like a distributed NFS backend. You can store the data on multiple devices, in multiple forms (as long as they all talk iSCSI). You can also have two storage sites (geographically separate) connected by fibre and use those for storage. same as NFS. while with iSCSI you have exported whole devices that can't be really shared with ease. and 100 times more expensive of course that just a cheap PC with cheap IDE drives.. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI support
In the last episode (Nov 22), Wojciech Puchar said: from people. ICBW but to me it seems that iSCSI is like a distributed NFS backend. You can store the data on multiple devices, in multiple forms (as long as they all talk iSCSI). You can also have two storage sites (geographically separate) connected by fibre and use those for storage. same as NFS. while with iSCSI you have exported whole devices that can't be really shared with ease. and 100 times more expensive of course that just a cheap PC with cheap IDE drives.. Whole devices accessed directly can be a lot faster than NFS, since the client doesn't have to constantly ask the NFS server whether the file it's currently accessing has changed. And when a cheap IDE in one of the 100 servers in your server room goes out, you have to find the server, figure out which drives it has in it and which RAID controller it has, go to your spares cabinet and get the right spare, swap the drive, load your raid management software, and rebuild. Unless you have a hotspare in each computer, but that's quite a lot of wasted disks. With a iSCSI/FC SAN setup, you probably have a couple hotspares configured in your array already and it's rebuilt automatically. If a server needs a few more TB or storage, simply create a new LUN and make it visible to the server. If you want to set up failover (or are running an OS that has clustered filesystems), make one LUN visible to multiple machines. There's also nothing that says the disks behind the iSCSI array can't be cheap IDE drives. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI support
just a cheap PC with cheap IDE drives.. Whole devices accessed directly can be a lot faster than NFS, since the client doesn't have to constantly ask the NFS server whether the file it's currently accessing has changed. any problem to add such option to NFS?? with iSCSI you just CAN't do it. anyway this asking isn't bandwidth intensive, while adds delays. and it may affect of transfer speed for ONE process reading one file, but not multiuser system. And when a cheap IDE in one of the 100 servers in your server room goes out, you have to find the server, figure out which drives it has in it and which RAID controller it has, go to your spares cabinet and get the if company having this 100 servers (must be really huge company or really bad software using to need 100 servers) and their IT managers don't know what it where and don't know few basic unix command to localize the problem source - then here is a problem, and any kind of SAN won't fix it. the real fix is to employ someone more competent. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI support
Wojciech Puchar wrote: Whole devices accessed directly can be a lot faster than NFS, since the client doesn't have to constantly ask the NFS server whether the file it's currently accessing has changed. any problem to add such option to NFS?? with iSCSI you just CAN't do it. anyway this asking isn't bandwidth intensive, while adds delays. and it may affect of transfer speed for ONE process reading one file, but not multiuser system. Regardless of whether iSCSI is any good, it's a common access method for SAN devices, and from what I've been told, may be the *only* access method. So in heterogenous (read windows dominated) environment where you want to be able to access these things, an iSCSI initiator for FreeBSD can only be a good thing. --Alex ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: iSCSI support
iSCSI enables block access to drives over IP. There is only so much you can do with NFS and SMB. -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Wojciech Puchar Sent: November 21, 2005 6:25 PM To: Josh Endries Cc: freebsd-questions@freebsd.org Subject: Re: iSCSI support and growing. I'm currently looking at a Coraid AoE (ATA-over-Ethernet) solution since it seems to have good support for FreeBSD and Windows drivers in the works. On the other hand, iSCSI has Windows support and FreeBSD in the works. stupid question: can anyone explain me the sense and adventages of iSCSI compared to say NFS? for me it's just some more layer to take lots of $$$ from people. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI support
affect of transfer speed for ONE process reading one file, but not multiuser system. Regardless of whether iSCSI is any good, it's a common access method for SAN devices, and from what I've been told, may be the *only* access method. So AFAIK it's SCSI over FC, SCSI over IP was next probably to eliminate expensive FC, that was invented first to make things more expensive. looks like politicians - first they get 1000$, then give 100$ back and say how much they gave ;) anyway - for already existing iSCSI devices driver won't hurt of course, but i'm sure nobody that understand things won't invest in such technologies. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI support
On Tue, Nov 22, 2005 at 07:13:45PM +0100, Wojciech Puchar wrote: anyway - for already existing iSCSI devices driver won't hurt of course, but i'm sure nobody that understand things won't invest in such technologies. I've been looking at iSCSI, but if someone can suggest a better alternative I'd be happy to use it, as I haven't bought anything yet. I have 3 datacentres connected by 12 core gig fibre (only using one pair at the moment, but the fibre is there for future use) each connected directly to the others. I want a system that I can start off with one disk server in one datacentre, and then step it up to have mirrored disk servers in each of the other datacentre's which are kept up to date in real time and can take over instantaneously if one of the others fails. It must also be scalable (non destructive resizing of the system) and support both linux and FreeBSD. I am willing to wait for this, but can anyone point me in the right direction. iSCSI seems to be it, but I'm not sure. -John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
iSCSI support
I read in the status report that work is being done on iSCSI, which is awesome. We're putting in a SAN at work, starting at probably 8 TB and growing. I'm currently looking at a Coraid AoE (ATA-over-Ethernet) solution since it seems to have good support for FreeBSD and Windows drivers in the works. On the other hand, iSCSI has Windows support and FreeBSD in the works. Has anyone out there had experience with either iSCSI or Coraid/AoE on FreeBSD for a SAN? I'd like to know what NICs/HBAs and stuff works well and what doesn't, if anyone has experience with it. Thanks, Josh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI support
and growing. I'm currently looking at a Coraid AoE (ATA-over-Ethernet) solution since it seems to have good support for FreeBSD and Windows drivers in the works. On the other hand, iSCSI has Windows support and FreeBSD in the works. stupid question: can anyone explain me the sense and adventages of iSCSI compared to say NFS? for me it's just some more layer to take lots of $$$ from people. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI support
On Tue, Nov 22, 2005 at 12:24:49AM +0100, Wojciech Puchar wrote: and growing. I'm currently looking at a Coraid AoE (ATA-over-Ethernet) solution since it seems to have good support for FreeBSD and Windows drivers in the works. On the other hand, iSCSI has Windows support and FreeBSD in the works. stupid question: can anyone explain me the sense and adventages of iSCSI compared to say NFS? for me it's just some more layer to take lots of $$$ from people. ICBW but to me it seems that iSCSI is like a distributed NFS backend. You can store the data on multiple devices, in multiple forms (as long as they all talk iSCSI). You can also have two storage sites (geographically separate) connected by fibre and use those for storage. -John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
NDAS or iSCSI
Is there a mature implementation of either iSCSI targets or NDAS (Ximeta) for FreeBSD? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NDAS or iSCSI
In the last episode (Sep 06), Ansar Mohammed said: Is there a mature implementation of either iSCSI targets or NDAS (Ximeta) for FreeBSD? There were at least two attempts at an iSCSI driver, but neither ended up releasing anything. ximeta's web site says NDAS is patented, but it looks similar to FreeBSD's geom gate server. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI (revisited?)
- Original Message - From: Justin Bennett [EMAIL PROTECTED] To: FreeBSD Hackers freebsd-hackers@freebsd.org Cc: FreeBSD Questions freebsd-questions@freebsd.org Sent: Monday, April 04, 2005 5:30 PM Subject: iSCSI (revisited?) All, I was wondering what people thought of iSCSI and FreeBSD. Is it a viable option for creating SANs? I want to move away from tape backups, and have numerous production FreeBSD machines that I need to back up data from. Any other ideas for a disk to disk backup solution that people have used? Thanks, Justin Justin, what I'm currently using is the following for just that: Promise Vtrak 15100 with 15 250gb sata's, connected to a dual channel Adaptec 39160 housed in a Compaq ML 330 running FreeBSD 5.3. The Vtrak has 2 logical arrays assigned, where my other 14 servers (windows and freebsd alike) back up to one or the other arrays. I have one array shared via nfs for the bsd boxes to back up to and the other is samba shared so that windows systems can back up to that one. So far, it's worked well for me. All I need to do now is get the company to realize they still need tape if they want long term storage and then I can chain that to the Promise raid and have it back up to take during the day and still have my backup window in the early morning hours. -- Micheal Patterson Senior Communications Systems Engineer 405-917-0600 Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI (revisited?)
All, I was wondering what people thought of iSCSI and FreeBSD. Is it a viable option for creating SANs? refrase question. I want to move away from tape backups, and have numerous production FreeBSD machines that I need to back up data from. for one, it depends on how deep are your pockets, 2nd the size of your data. 3rd how fast do you need to access the data, 4th from where, etc, etc, etc. Any other ideas for a disk to disk backup solution that people have used? We went the NAS/NFS route for most of our uses, and ONE application that has a huge database has a fiber channel link to the filer. The NAS is Raid4, with hot standbys, and we have not had a serious meltdown in years. Before NAS, we had to upgrade our servers, dump|restore, and the down times were getting larger, with the NAS, just add some disks, and no one is the wiser, life goes on. We still do tape backups, and move the tapes out of our premises just in case a major disaster hist us (someone misspoint a ICBM perhaps :-) having said all this, we are experimenting with iSCSI, and the numbers are not bad, about the same as NFS/NAS. Still, NFS is still our prefered solution. danny PS: AFAIK, there is only a iSCSI intitiator (beta), and no target for FreeBSD. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
iSCSI (revisited?)
All, I was wondering what people thought of iSCSI and FreeBSD. Is it a viable option for creating SANs? I want to move away from tape backups, and have numerous production FreeBSD machines that I need to back up data from. Any other ideas for a disk to disk backup solution that people have used? Thanks, Justin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI (revisited?)
Justin Bennett wrote: All, I was wondering what people thought of iSCSI and FreeBSD. Is it a viable option for creating SANs? I want to move away from tape backups, and have numerous production FreeBSD machines that I need to back up data from. Any other ideas for a disk to disk backup solution that people have used? Thanks, Justin For disk-to-disk backup take a look at BackupPC (don't let the name fool you it supports *nix clients). The nice thing about BackupPC is it does file pooling which saves *a lot* of space. John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI (revisited?)
Justin Bennett wrote: All, I was wondering what people thought of iSCSI and FreeBSD. Is it a viable option for creating SANs? I want to move away from tape backups, and have numerous production FreeBSD machines that I need to back up data from. Any other ideas for a disk to disk backup solution that people have used? You should check out rsnapshot. It does disk to disk backups either locally, or via ssh. I am using it to snapshot about 2TB of data to a 10TB (total) SAN, based on fiber channel. All FreeBSD backend, with assorted servers I'm backing up. Eric -- Eric AndersonSr. Systems AdministratorCentaur Technology A lost ounce of gold may be found, a lost moment of time never. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
iSCSI support?
What version(s) of FreeBSD, if any, support iSCSI storage connectivity? Is there an open source FreeBSD iSCSI driver which would work with ethernet adapters listed on the hardware compatibility lists? Do FreeBSD drivers exist for iSCSI HBAs by Adaptec, Alacritech, Qlogic and/or Intel? Any relevent information would be most helpful. Thanks! Sam Farmer Systems Engineer Cambridge Computer Services, Inc. Artists in Data Storage Tel: 781-250-3212 Fax: 781-250-3312 www.cambridgecomputer.com [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: iSCSI support?
In the last episode (Feb 28), Sam Farmer said: What version(s) of FreeBSD, if any, support iSCSI storage connectivity? Is there an open source FreeBSD iSCSI driver which would work with ethernet adapters listed on the hardware compatibility lists? Do FreeBSD drivers exist for iSCSI HBAs by Adaptec, Alacritech, Qlogic and/or Intel? Any relevent information would be most helpful. Thanks! You're in luck ): Last week, Danny Braniss posted that he was looking for testers for an iSCSI initiator (for regular NICs) that he just finished. http://lists.freebsd.org/pipermail/freebsd-scsi/2005-February/001740.html -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
iSCSI support in FreeBSD?
Is there planned iSCSI support in FreeBSD 4 or 5. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
