| 1 |
I've recently been experimenting w/ this, and while the iSCSI target |
| 2 |
patch for 2.4.22 appears to work for later kernels (I'm using 2.4.26), |
| 3 |
the kernel module is complaining about a missing symbol, prefetch. |
| 4 |
Anyone know which kernel option gets this symbol into the kernel or a |
| 5 |
module? |
| 6 |
|
| 7 |
On Tue, 2004-04-20 at 14:30, Bryn Hughes wrote: |
| 8 |
> Doesn't look like I've had any bites out there so I'll share my |
| 9 |
> findings at least for any future googlers... |
| 10 |
> |
| 11 |
> The good news is iSCSI on Linux works. I have been able to export |
| 12 |
> block devices from one Linux machine and mount them on another. |
| 13 |
> Apparently the Windows drivers are well tested too but I don't have any |
| 14 |
> Windows machines to test with. The initiator sees the exported iSCSI |
| 15 |
> LUN as if it were a locally attached SCSI disk. If you export an LVM |
| 16 |
> volume it appears to the remote machine as a local SCSI disk and you |
| 17 |
> can do all the usual stuff to it - i.e. you need to either create a |
| 18 |
> partition table or use lvm on the remote machine to portion out your |
| 19 |
> virtual device. |
| 20 |
> |
| 21 |
> The bad news is the iSCSI target driver is lacking a few key functions. |
| 22 |
> It doesn't seem to handle resizing volumes very well - I tried |
| 23 |
> resizing an exported LVM volume and all hell broke loose. The biggest |
| 24 |
> problem however is that it doesn't appear to let you make configuration |
| 25 |
> changes without restarting the target daemon. This is a major problem |
| 26 |
> as it means you have to unmount _ALL_ iSCSI volumes before you can add |
| 27 |
> a new one on the target server. This wouldn't make for much of a SAN |
| 28 |
> if every time you wanted to make a configuration change you had to down |
| 29 |
> all your servers! |
| 30 |
> |
| 31 |
> So here's hoping that more developers will join in on the iSCSI target |
| 32 |
> project listed below at ardistech.com. There's definitely something |
| 33 |
> brewing here which will make SAN's a whole lot cheaper and easier to |
| 34 |
> implement for the average environment. Give it some more development |
| 35 |
> time and it will actually be viable! |
| 36 |
> |
| 37 |
> Bryn |
| 38 |
> |
| 39 |
> |
| 40 |
> On Apr 15, 2004, at 6:48 PM, Bryn Hughes wrote: |
| 41 |
> |
| 42 |
> > I'm looking for experiences implementing iSCSI on Linux - not just as |
| 43 |
> > an initiator but as a target as well. I've found these two projects: |
| 44 |
> > |
| 45 |
> > This is the iSCSI initiator project started by Cisco |
| 46 |
> > http://sourceforge.net/projects/linux-iscsi |
| 47 |
> > |
| 48 |
> > This is the ardistech iSCSI target project |
| 49 |
> > http://www.ardistech.com/iscsi/ |
| 50 |
> > |
| 51 |
> > In theory it is possible to create iSCSI volumes using EVMS or similar |
| 52 |
> > and then mount them as block devices over ethernet to another host |
| 53 |
> > (could be Windows, Novell, Linux, OS X, whatever). Basically you can |
| 54 |
> > build yourself a SAN using free software and normal ethernet |
| 55 |
> > (obviously gigabit preferred). |
| 56 |
> -- |
| 57 |
> ~ |
| 58 |
> ~ |
| 59 |
> :wq |
| 60 |
> |
Archives