Slashdot Mirror
Turning a PC into a Firewire-Based SAN?
Rachovenov asks: "So I've finally plunked down the money for one of those new, shiny Powerbooks, but they don't have much storage. My old PC is just sitting here with 2 identical 250 gig disks spinning away and an empty firewire port. There's even a hardware RAID controller in there somewhere. So why not use it as a low cost RAID 1 array for the Powerbook when I'm at home? Has anyone done this? How could I make it so that Mac OS X just sees it as a couple of Firewire drives?"
I believe he wants to turn his PC into a dum-firewire raid box for his pa-pa-pa-Powerbook. As in: Firewire from his Powerbook to his Pc, so the Mac see's it as a storage device. I dont think there is a way to do this now.
No I didnt spell check this post...
You wanted the PC itself to be act as a firewire drive?
Good luck. Macs have this built into the firmware, not PCs. I don't think it's even on anyone's radar. But I don't imagine it's too difficult to write something that could do the job using libraw1394 and the SBP2 documentation.
Good luck!
THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
iscsi on linux
Gyrate Dot Org - "Where high-tech meets low-life"
I haven't seen anything like that either.
I think it would be end up being easier to just use the ip over firewire stuff and just make it appear as a network drive. (or any network, just said firewire because has a listed max of 400 Mb/s versus 10/100 ethernet having a 100Mb/s max)
Either that or just buy some $50 (or less) firewire enclosures.
Pop a gigabit ethernet card in your big machine and use a regular network connection. No need to get complicated with Firewire networking or whatever.
The ratio of people to cake is too big
Errrr...Did you read the question at all? That is not an answer to the question. He's not looking for a Firewire disk container, but to turn a PC into a firewire device.
AFAIK, IIRC, the only way to do this would be to raid the drives on the PC and export them via NFS or SMB and set up TCP/IP over firewire.
I am, and always will be, an idiot. Karma: Coma (mostly effected by
Not unless he's running RAID 1. Not everyone is running a stripe.
True, I didn't read carefully.
TCP/IP over firewire.
run it as a samba server, but connect through the firtewire. google it...it'll work and be fast.
Do a minimal MINIMAL Linux or FreeBSD install. I mean just as small as you can get, but include NFS and IP-over-Firewire.
That's about it really, set up a nice link to mount your device when you come in, plug in your firewire. Heck, I think you can configure the automounter to detect when the firewire network becomes available and mount it for you. That's really all there is to it. Should work out pretty well. On a side note, if you plug in a third drive, even if your SCSI card doesn't support it, you could use Vinum on FreeBSD or LVM on Linux to add capacity, and at least on Vinum you can do RAID5 or RAID10. It won't be as fast as hardware RAID, but hey when you're going cheap, you use what you can. Besides, I somehow suspect that you're wanting capacity over speed anyway, and if that's the case, use the best redundancy you can, right?
Karma: Chameleon (mostly due to the fact that you come and go).
I hate to point it out, but that is not the solution you are looking for (waves hand).
You already have a PC, and the two disks built inside. Mirror or stripe the drives in the system (your choice, I'd got for a mirror) and then install Linux or BSD or whatever server-ish operating system you want on the box with the right services (Samba, NFS, whatever). Connect to it with IP over firewire, Ethernet, or gigabit ethernet if the old system supports it (the laptop does).
This will allow the system to keep running when you are not around, will allow you to use the disk over that fancy wireless connection on your new Po-po-po-powerbook!. If you put SSH on the box I'm sure you'll figure out how to access your home disk from the road (for bonus points roll your own remote file access solution based on some creative web based interface running on port 443 that no one will ever block).
Last but not least, you'll be able to access the disk from the PowerMac system you'll eventually buy when you realize that the Powerbook is just a touch slow, the keyboard is not so comfortable, and the trackpad is complete crap (mind you, I have a 17" PB myself and love it to death, but all of the above are true and that's the reason I use a Bluetooth keyboard and mouse with it when it's "docked" at home).
-Jack Ash
See a previous Slashdot story entitled Home-brewing a 1.2TB IDE to Firewire Monster. He constructed a huge firewire "disk" out of a nice case and most importantly, a couple firewire-IDE bridges. It's not PC-based, however, it's a dumb array of drives.
As people have more and more old machines lying around, having a live CD with a single purpose operating system. I think there are already distributions that transform a PC into a router, but changing an old PC into a firewire hard drive enclosure looks like an interesting idea.
One advantage of this approach over installing a file-server is that the hard drives are seen directly by the OS, this means you can boot of them, do low level manipulations (like formatting them), directly from the client machine.
One such distribution I would like to see (one can dream), is that changes an old PC into a advanced dock for a laptop. Typically, a thing I can connect my laptop to, and I get to use the peripherals of the PC: hard-drives, CD-drive, keyboard, mouse, heck even the floppy drive.
The goal would be to have all those devices recognised as being devices attached to the laptop, i.e no client server protocol to share them - basically the PC would pretend to be a firewire or USB hub with a lot of devices attached.
Maybe I would even make sense to use the sound-card of the PC. Not so long ago I would have suggested also to access the display of the PC and use its CPU as a powerful GPU, but given the graphical cards one can now find in laptops, this makes no sense.
I have a mac geek on our PC network, and every time he saves a file onto a network share, it also saves a useless file next to it with the same file name, but a dot-underscore before it. Is there any way to get him to stop doing this short of beating him with his own powerbook?
Bork!
That's for the resource fork. That file may be useless to you, but depending on what type of file it is, it may be quite important to him. Don't delete them before you understand the nature of the resource fork.
I've done a fair number of tests comparing speeds from moving files via 10/100, gigE, firewire, and IP over FireWire. Long story short: 100bT and anything over firewire are neck-and-neck. Gigabit Ethernet blows them away. So set up the box as a server, using gig-E if possible. Not sure about the PC, but you can connect two gig-E Macs with a straight (*not* crossover) cable and they'll automagically connect properly and you get gig-E speeds--like moving a 650 MB disk image in 30 seconds instead of 90 seconds over 10/100, IP-over-FW, or to a firewire disk.
Yeah, it'd be nice if you could just put the PC into target disk mode like a Mac, but you can't. There are some advantages and disadvantages, but I think the advantages of a server--even ignoring the whole "server setup is easy, target disk mode with Intel hardware is just about impossible" thing--would win over using it as an attached disk.
Among other things, you can tuck it anywhere--it doesn't have to be a firewire cable's length away. And since it's networked based, it's easier to share, and can even be accessed (thought more slowly) via wireless.
Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
If you're running samba as a file server, you can set those files to hidden or veto them relatively easily. I'm not sure how to turn them off on the Mac side, so I just set them to hidden on the server.
If you're running windows servers (that's just weird), then I'm not sure what to tell you. Set up a scheduled task to get rid of them...
http://developer.apple.com/macosx/bonjour/ How about to create a "file system exporter" in Bonjour technology, that should be great for Macs.
http://oss.oracle.com/projects/endpoint/ - it turns a linux machine into a SBP-2 endpoint.
Quando Omni Flunkus Moritati
He has no use for them, and they don't seem to do anything special. The only things he does on our peer to peer network is move around some word files, zip files, pictures, and dwg files. He would really like to play nice on our network and not leave these files, but he has no idea how. He can't even delete them himself, because his powerbook refuses to show him these files.
I can run a scheduled delete script on the network's PC's, but is there anything he can do, short of buy a PC? It really is obnoxious of macs to do this by default on PC networks.
Bork!
I had the same space issues with my Toshiba notebook ... Until someone pointed out USB 2.0 drive cages.
I snared 2 ($25 a piece) and put my 2 120gig drives in. Plug em in, Windows (I know you have a Mac, but it should be similar I'd hope) detects them and I've got 240gig of space on top of the 20gig that my laptop has. easy as that.
There are also firewire cages out there if you're hooked on that.
Cheap and easy. The only downside I've found so far is that, be cause the drives are in cages and independantly powered, they never stop spinning until you unplug them. I don't see the need to have my drives spinning all the time, especially when my laptop isn't even there, so I put them on a power bar to make turning them off easy when it's time to take the laptop on the road.
$0.02 CDN.
We emerge from our mother's womb an unformatted diskette; our culture formats us. - Douglas Coupland
Its how mac OS stores some metadata for the finder. (File labels and such) the best bet would be to use find from a crontab to go and get rid of them every so often.
Erlang Developer and podcaster
What's so obnoxious?
/home?! .gtkrc! BLAST!
/etc, too?! Is there no shame?!
.xvpics directory, but then, it saved my ass a time or too..
Ewww! A Thumbs.db file on my drive!!
Ick! What's this in
Gasp! Here in
Are they duplicate files, or little 30 byte file descriptors? GIMP used to burn me with that damned
Is it that big of a deal? The script does it's job, so what't the beef?
"What's so obnoxious?
Ewww! A Thumbs.db file on my drive!!"
I can turn off the creation of thumbs.db files if I'm visiting someone's non-pc SMB network with my laptop. My friend can't stop his mac from creating a fork file for every file he copies across the network. He would like to avoid the hassle of explaining them and how to get rid of them every time he connects to someone else's network. Especially if the peer to peer network is run by some clueless people. He would rather just disable his mac from creating these files on network shares, because he never needs the files anyways, and its a hassle for him to delete.
Do you understand?
Does anyone have and explicit guide for something like this that works for editing of DV content in Avid or Final Cut Pro? Right now I do all my work off of individual firewire drives, but I'm tired of the clutter and worrying about one of the drives failing and not having sufficient backup for it. I have a couple of IDE drives lying around, and would love to set up something similar to a RAID 5 setup so I could sleep a little better at night. Some people have mentioned a server setup with GigE, which would also work, but does it actually work like a local disk would with picky Avid software? What kind of boxes are you guys building for it (mobo, processor, ram, OS, etc)?
Nothing from nowhere I'm no one at all
I also suggest ISCSI.
I know you want to bank on your firewire connections. Go for it.
Iscsi would give you the ability to connect to shared block devices in your machine via TCPIP networking. If you do that over firewire, or Twisted pair 10/100, or wireless, you can leverage alot more then a direct connection. For one, you would not have to be within what ever limit is imposed by your firewire cabling situation.
ISCSI can be implimented entirely in software. There are ISCSI target (host) software solutions that let you turn a PC (X86 is what I know and have played with) into a destination (hosting the drives). You can allocate the drives as you desire. And it is fast.
However, I am not certain on the MAC software side of the deal. There is one company (at least) called ATTO who claim to have a software ISCSI initiator called XTEND SAN. But it seems they have been talking about it for a while, with no release. ARDIS also claims to have one, but only for OEM companies.
I have played the software route on Windows and Linux. It is fast and cool to do it all in software. A hardware ISCSI initiator (think scsi card combine with ethernet card) costs way to much for the casual user ($500 +).
And yes, none of this has any meaning to you if there is no software ISCSI initiator for your mac.
(umm.. you also didn't really state what your OLD PC really is.. Is it a PC in the Windows/X86 sense? Or is a PC in the sense of another Mac? (do we all naturally assume PC means Windows?)
> Do you understand?
With a slashdot id of 143245 you either got your account from ebay or they tried that hibernation thing with you.
This place is full of Mac and Linux Zealots comparing the latest OSX/Linux release to Win3.11 or Win95
it's the only post in the whole thread that actually answered the question!
...the RAID isn't going to give you anything. Having a single 500GB drive instead of spreading your data across 2 drives would be more convenient. I do agree with others here that using GbE instead of firewire would be the easier, faster & cheaper option. Unibrain http://www.unibrain.com/1394_products/1394_network ing/firenet_mac.htm has a IP over FW solution for the Mac but it costs just as much as a GbE card.
CN=poolmeister.OU=lurkers.CN=slashdot
umm, how can I be redundant when I am the first to post a reply saying this? Stupid mods =)
No I didnt spell check this post...
500GB? You're thinking of RAID0 then, where data is striped across disks. RAID1 is a mirror set, i.e. both disks contain identical data.
I think, therefore I am. I think?
Exactly... That's what I meant, but was too lazy/dozy to fully explain (or correct the formatting of the post). :/
CN=poolmeister.OU=lurkers.CN=slashdot
Well, here it's a peer to peer XP network in a small office. How would I veto those kind of files on the network layer, so they don't get transmitted? It's a temporary fix, but it would help in this office.
._ files, and why he should have access to another machine to delete them across the various machines on the network. As a travelling consultant with a mac, the only thing that makes good business or pr sense is to prevent these files from going out in the first place, or have some way his mac can auto-delete them after.
Since my colleague with his powerbook does move around a lot, and connects to various networks big and small, is there any awy he can put a filter on his outgoing network traffic to block these files? He really doesn't want the hassle of having to delete them after the fact on someone else's network, since his mac can't see the files in the first place. And he also doesn't want to explain to some clueless office manager why his mac peppers their computers with
Do you know of any simple solution on the mac that he can implement?
Thanks.
I'm not sure, but I'd suggest digging around in google to find a way to disable compatability resource fork generation or somethign along those lines. That's OS X's way of storing resource forks on a non-HFS filesystem, and I could have sworn that there was a mount option or something that could be set to disable that. Check out macosxhints.com as well - theres lots of useful stuff up there along these lines.
As far as blocking them at the network level - you'd probably need a proxy or a different file server. The file server won't help if you're peer to peer, and I don't know of any smb proxies, so you're probably stuck with figuring out how to disable them on OS X...
What does that make me?