Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: bbond007 on October 23, 2011, 05:26:35 PM
-
Hello!
I'm having a problem with FFS. I read that it is supposed to support up to 107 characters, however that does not seem to be the case in practice. I'm having an issue with SaMBA in particular.
I'm connecting to a share on my windows 7 PC where I have a bunch of ADFs with longish file names. I'd like to copy those files over to my drive called BACKUP: but the copy just stops when it encounters a long filename. I would like these files on my amiga and I would also like preserve the existing filenames.
I have attached PNGs of my configuration for that drive in HDToolBox.
Do I need to use a new filesystem for that drive? Also would a new filesystem speed up that drive?
Thanks,
_nate
-
Not sure, but I think it's more likely a limitation of Samba. Try copying some to RAM: instead and see if you still run into trouble. RAM:'s file system is different.
-
Not sure, but I think it's more likely a limitation of Samba. Try copying some to RAM: instead and see if you still run into trouble. RAM:'s file system is different.
yeah, it seems to be chopping the filename at like 30 chars when copped to RAM:
I'll try and FTP the files over.
Thanks.
_nate
-
I would guess a limitation of Samba too. 30 characters seems a strange place to stop unless it is Samba. It sure isn't FFS.
-
FFS is limited to 30 char filenames.
If you want longer filenames then you need to install PFS3 which is free, fast, and supports the full 107 chars that AmigaOS allows.
-
FFS is limited to 30 char filenames.
If you want longer filenames then you need to install PFS3 which is free, fast, and supports the full 107 chars that AmigaOS allows.
OK, I have redone that drive with PFS3 and when I formatted it the drive and the PFS3 dialog came up, so I know the drive is now formatted PFS. Just to be sure, I checked it in HDtoolbox and it shows FileSystem "Custom" Dostype PFS\03.
I still have the same issue. I have tried to copy these files via USB, FTP (via AmiTradeCenter) and SAMBA(using both CLI and GUI). All files get cut off at 30 characters.
What gives? I'm using 3.1 with ClassicWB ADV. It uses Scalos instead of Workbench. Is Scalos the issue?
thanks
_nate
-
FFS is limited to 30 char filenames.
If you want longer filenames then you need to install PFS3 which is free, fast, and supports the full 107 chars that AmigaOS allows.
Yes, I think it's correct.
FFS is really limited to 30 characters: more than the PC DOS old style 8+3, but still not that much for big descriptions.
BY!
-
Yes, I think it's correct.
FFS is really limited to 30 characters: more than the PC DOS old style 8+3, but still not that much for big descriptions.
BY!
Is there a filesystem that does support over 30 characters? I tried PFS. No Dice...
-
SFS should. There's also FFS\07 from OS4 Classic which exists in 68K, but I could never get it working.
-
Is there a filesystem that does support over 30 characters? I tried PFS. No Dice...
RTFM!
Default setting is compatible to FFS. You can change this by shell commands.
-
RTFM!
Default setting is compatible to FFS. You can change this by shell commands.
oh. duh!
setfnsize
trying again...
I just hope I don't have filenames over 107 :)
thanks
_nate
-
setfnsize
I recommend using the pfs format command and setting the file name size with it.
-
RTFM!
Default setting is compatible to FFS. You can change this by shell commands.
But the limit is still hard coded in programs like Magellan, afaik.
So not a fix-all.
#6
-
Magellan is a bad example because it has an option for max. filename length. Older versions of DOpus might not. Workbench can be changed to long file names since 3.5 IIRC.
However, it's dangerous to set Workbench and the like to long file names and using a file system which cuts names off after 30 characters. For example let's imagine that "long_filename" becomes "long_file" and "long_filename.info" becomes "long_file", too, then the icon will overwrite the actual file. So be carefull to tell your copy program the real max. file name length the file system can handle.
-
I recommend using the pfs format command and setting the file name size with it.
Why?
-
I recommend using the pfs format command and setting the file name size with it.
Why?
I've had trouble using the regular format from AmigaOS 3.x. It's simpler to create the partition the way it's wanted than to modify it later too.
-
Use quick format. Complete format is not necessary, it only produces hot air anyway. And wastes a lot of time.
-
However, it's dangerous to set Workbench and the like to long file names and using a file system which cuts names off after 30 characters. For example let's imagine that "long_filename" becomes "long_file" and "long_filename.info" becomes "long_file", too, then the icon will overwrite the actual file. So be carefull to tell your copy program the real max. file name length the file system can handle.
If you are using Shell it will cut long filenames anyway.
-
Use quick format. Complete format is not necessary, it only produces hot air anyway. And wastes a lot of time.
I'm using a OCZ SSD so I just chose the quick option...
The PFS docs do say to do a full format and the reason given is so that it will be easier to recover the drive with disk editor in case of corruption because the quick format option leaves all of the old data intact.
Disk editors are really beyond the scope of what I know how to do anyway...
_nate
-
If you are using Shell it will cut long filenames anyway.
That is not the behavior I'm observing.
When you do issue a dir, the filenames are cut off, but I'm not seeing it cut any names short, and I'm using the full names to manipulate the files. Thank god for King Con so I don't have to type all that!
I created some MPEG video files from movie file that originally had a really long file name. I had the transcoder program split the movie into 15 minute segments, which appends .001 .002, etc on to the original filename making the unique part way past 30 characters.
I used samba to mount a windows share and I copied the MPEG files to my PFS formatted drive via the CLI.
Everything is fine...
Now, I am running into an issue where I have so many files in one directory that the computer crashes if I try to open that folder... That may be a Scalos issue. I'll just use the CLI..