Why would I be unable to transfer a photoshop or adobe illustrator file from my (successfully) networked Buffalo terastation back to my 1 GIG jump drive on OS X? :confused:
[[BTW-the jump drive works well with other local files, isnt locked ,isnt full, it has mega room but is formatted in FAT16, the file to copy is usually just 50 megs in size]];)
The terastation is preformatted in XFS and the G4 system I am using is on HFS+. The connection to the Buffalo (destination)terastation is ethernet with TCP and appletalk the source drive is a LACIE the BIgger disk (on firewire) and I am able to see all drives in question. All mount just fine to the desktop and I can copy files from one drive to another and open them however I cannot transfer files from the networked Terastation to my desktop then to the jumpdrive directly or directly from the terastation to the jumpdrive.
(error -50 actually). :confused:
the gory details....
I have a G4 MAC with OS X and my task is to transfer oodles of info (about 350GIGs worth) to a network storage device. This destination device is a Buffalo Terastation 1 Terabyte (huge):eek: which came preinstalled with the XFS file system on a RAID 5 array. The source is a single terabyte LACie drive in RAID 0 (all 4 drives meshed into one large partition) on HFS+.
It boils down to this... the source has plenty of misnamed files in it --the use of forward slashes and backward slashes in the file and folder names is very common throughout the root directory of the source drive. Thus far it hasn't been a disaster to work with but I have read that "weirdness" can occur from this naming scheme in UNIX as slashes essentially commands.
FOr example...illl get errors stating the source already has a copy of the new file to copy ....when it clearly doesnt as I make a new share...its very odd but anyway...
My thinking is there are file(s) within whatever folder I am copying that are incompatable with FAT16 but I may be overlooking something even more sinister:eek: .
Any file - big or small - that I transfer from the networked Buffalo to the desktop then to the jumpdrive wont happen..in fact the system wont let me edit copy edit paste it either...any idears?? (all props to Paul Teutel Sr.)
the fate of all mankind rests on your help.......:(
hayne
10-04-2005, 09:19 PM
Any file - big or small - that I transfer from the networked Buffalo to the desktop then to the jumpdrive wont happen
Huh? Once you transfer the file onto your G4's Desktop, it is on the G4's disk, so the fact that it came from the Buffalo should be irrelevant.
First off, verify that you can copy files of similar size onto the jump drive from your G4.
Then try renaming one of the files that you got from the Buffalo - e.g. name it "foo" - and then copy it to the jump drive.
voldenuit
10-04-2005, 11:15 PM
I'm afraid that slashes in filenames are a really Bad Idea on about any filesystem other than HFS(+).
HFS uses the : as directory-seperator while all decent Unix filesystems use the / and the crappy bunch of FAT-fs use \ becaus some dork back in DOS 1 brilliantly used the / as an option seperator for a couple of commands.
Bottomline:
You need to rename your files to comply with the naming standards of the filesystems used by your NAS.
Also stay away from filenames asking for trouble such as containing * ? | & "rm -f" etc.
And you will have trouble with files still using resource forks.
If I recall correctly, FAT16 just uses the 8.3 file name standard, which means not only may your files have illegal characters, they may simply be too long. FAT16 may be truncating the name, which it then reports as belonging to another (similarly truncated) file name.
Are you SURE it is FAT16? I don't think FAT16 supports partitions of that size. Or perhaps I haven't understood your configuration properly yet.
Joe VanZandt
MACINSOFT
10-05-2005, 10:42 PM
guys ,,,my bad on something.
The Jumpdrive is actually showing as Fat32 ... so the long filenames thing shouldnt be an issue for me but the insane amount of / /:mad: \\ slashes in the folders to be copied will be no matter what. :( <<Incidently, FAT16 can handle up to 2 gigs worth of info on a partition and FAT32 in theory can see up to 2 terabytes but only recently can LBA controllers can actually handle that much data. >>
So perhaps its just in the file name as I need to look deeper than the first level of each folder I am atempting to copy. I did try to change the folder name but inside each folder is a slew of more folders and files with who knows what kind of naming issues. I know one thing - FAT32 or not - Windows does not like slashes in file names and WONT let it happen on any drive it is writing to. :cool: I can be glad Im using OSx to make these transfers.
Reflecting now...being somewhat used to working around PCS and OSes of all sorts I just never thought someone would set up 360GIGs worth (yes thats freaking 360 GIGABYTES) of data all on a root of a drive with slashes in the names of the olders...perhaps even thousands of entries like this on the external drive.
The bigger question now is ...The destination NAS drive is formatted in XFS - should I be concerned since this will be in a mixed network environment of Windows 2000 and OS 9.2 OS X, ??? The network should convert all info into bits that the presentation and application layer will reassemble but why would they send this drive out preformated with Linux XFS?:confused:
and thanks for the input!
TOP
