hi there,

i have just bought a new sata hard drive a 750 gigs samsung with a ide-sata dongle, and i have to say, it works great! after connection to a free ide cable and few jumper settings attempts it booted correctly into my MorphOS 2.2 Ambient, and the HDConfig recognized whole capacity 750 gigs (698 real gigs) without any problems. I managed all my partitions as i wished, and it started to work flawlessly, i love the HDConfig, as it's not needed anymore to reboot the machine after changing the settings. Only pity is, that i can't setup partitions larger or equal to 128 gigs, so i setup few 120 gigs partitions, quickformated them, and everything really seams to be okay now.

when i was transfering data from my older 160 gigs harddrive, the copy speed in ambient was something about 17 megs per second.

problems: when i started to copy, say 25 gigs of some digital photos, i left the computer as it said it will take about 20 minutes... when i came back in about 30 minutes, only about 80 percent was done, and the expected time showed something like 15 hours or so, and the speed was falling down... don't understand why, i tried it second time with the same result. then i tried to disable the blanker, and tried another 24 gigs of data, and everything was just fine at about 16 megs/s. i really don't know, if this issue is a problem of the hard drive, or the dongle, or the ambient, or the blanker, will investigate more next week...

anyway, it's great to get such capacity for this money in my Pegasos2 machine.

bye, MarK.

When you like bigger Partitions use the old HDConfig from MOS 1.4 for setup.
And if you want to use them you need to set this command in user-startup "lock hd2: off" replace hd2 with your partition. I had no problems using this partition with 617GB only once with MOS unrar command from c:. I have filled the whole partition with 617GB just to test if something will go wrong and i loose data but everything was fine.
To your Problem i would blame the blanker they seem to consume most of the CPU cycles. Therefor you get slowdowns.

Good to hear those sizes work now ;) There was some useless limit in old SCSIConfig, which didn't allow you to use more than some 2xx gigs of HD... unless you tuned values by yourself as I had to do with my 320G disk (it's worked fine too after since though).

SFS works only with partitions under 128G, that's why there's limitation in HDConfig now.

Have you tried copying from shell to see if the speed problem occurs there? I'd recommend that in any case when moving system or making backup. With CLONE option you can be sure that all dates and protection bits etc are preserved. I'm not sure if Ambient does that... I tend to use lines "cd source:path/" and "copy #? dest:path/ all clone quiet".

BTW. was there still plenty of space on your destination partition when you tried to copy those?

well, there are lots of free gigs available, so there shouldn't be a problem with fragmentation. and last week i also defragmented all partitions on my old hdd.

when i got back to my computer, stopped the blanker, cpu wasn't very busy, but the files was transfered very slowly (like 400 kB/s) and it wasn't making any better after.

i tried to copy data with DirWork 1.62, and after some longer time i realised, it's also transfering data very slowly. i'll do some measurements next week.

bye, MarK.

ps: anyway, it's great to have that much free space now...

@ThePlayer

Seriously, the MorphOS Team does know better than you when it comes to SFS internals, so please stop such "advices", OK? The limit is there for a reason. If you just fill the partition with data, it is unlikely that something goes bad immediately. But use it for a longer period of time and it WILL break...

... and SFSDoctor won't be able to help you.

I know that you know it better, but i use this Partition with 617GB now over 10 month.
The only problem i had was a full HD when extracting a rar archive with the MOS unrar command. I fixed it by deleting some files on the HD after that i filled this HD with 617GB and i had no errors all md5s where ok.
So what know?
I know that i do this on my own risk but it works, and i am not the only one.
And if one day i lose data i wan't blame you nor the MOS-Team.
But i would prefer an Update to SFS that can use Partitions and HD with over 128GB and that MOS and the Filesystem could work without problems with Files >4GB.

SFS can't be fixed. Or rather, a fix will mean a new filesystem (DOSType) because the bug is in the SFS' structures (meaning this is not a bug in the code, but in the design of the filesystem).

so let's bounty the sfs2 with larger maximum limit :) with 750 gigs hdd the 128 gigs limitation isn't really big problem for me... but in future... that would mean sth like atleast 10 partitions on a single hdd? that WILL BE annoying... :)

bye, MarK.

Why do you need a single partition with 750000000000 bytes capacity?

let me ask you in other way, why should i have 6 partitions, when i don't want that many? :)

well, for me it's really not a problem

bye, MarK.

Quote:

Because its anoying to have a partition MP3-1, MP3-2, MP3-3, MP3-4, MP3-5, MP3-6, MP3-7 and 7 Mappings on every Windows/Settopbox Client for one MP3 share.
Just one reason.

@jacadcaps

And what about using bigger block size (e.g. 4KB), would it help to get stable SFS partitions bigger than 128GB?

@Crumb: It won't help, AFAIK.

Like Chain says: the blocksize is irrelevant.

I know jacadcaps will hate me for that
I use a blocksize of 8192 bytes and the size of my partition is 617GB
i filled it completly and checked the files with md5 all files where ok no problems. i use this drive now for over 9 month. I had only one problem after a month when i extracted a rar archive with the unrar command that is installed with MOS. I had 490GB free on the partition, and after 700MB of the extracted archive the partition was full. I solved the problem by deleting about 20GB of data on that partition. After i've done so the drive showed the right value i had about 510GB free space on it, so i started my test and filled the drive, like i mentioned befor without any problems. Since then i had filled the drive between 60-90% and never had any errors or problems again.
And as i wrote there are some other people on pegasosforum.de that uses partitions above 128GB without problems.
I know that i use it on my own risk and i will not blame anyone else only me if i lose date, but you know you can back it all up ;)

And now to the question why do you need such a big partition, for some of us it's all about porn but i like the idea of having all my multimedia files like mp3, pictuers, videos etc. on one big partition that i can share on the network or just to have all the files in one place. And don't need to have to split it up in 5 partitions.

[ Edited by ThePlayer on 2009/1/19 19:35 ]

well, i guess this is the right time for sfs author, to write, what are those problems with partitions above 128 gigs barrier, as it works, i guess it's supported, but as there is the 128 gigs limit, what's the reason?

thanks in advance!

bye, MarK.

Quote:

To me, such a big storage space is scary. Our company's full data warehouse database (filled with tons of redundant information) would fit ten times in your single hard disk.

Hey, how about writing an AmigaDOS handler that merges several partitions into a single volume? We do "weirder" things already, like mounting ISO files as volumes, encryption... Would it be very hard to do?

Perhaps the sensible thing would be for the network sharing software to serve more than one directory in the same shared resource. Does any operating system do that?

With MorphOS <=1.4.3 (LBA28 HD-Adressing) was a 128 GiB Limit for Partition/HD Size.
With MorphOS >=1.4.4 (with LBA48) the Limit is 128 PiB (1PiB =1024TiB)

With MorphOS <2.0 (32bit DOS) was a 4GiB Limit for Filesize.
MorphOS >=2.0 has 64bit DOS.

Only missing now a Filesystem with >128GB Partition /HDSize and >4GB FileSize. And all Flags, Comment... for full Compatibility with MorphOS /Applications.

ext2 (MorphOS Version): Is not usable for Files >4GB!
- Speed at <4GB (file with 6GB) around 25MB/s
- Speed at >4GB (same file with 6GB) around 700kB/s! Not even enough for low resolution movies!
(And has no comment, not all Flags and ... for MorphOS)

SFS:
1998 J.Hendrikx wrote over SFS:
http://www.xs4all.nl/~hjohn/SFS/features.htm
"Below you'll find a list of features which are already implemented in SFS.
...
Supports large partitions. The limit is about 2000 GB, but it can be more depending on the blocksize."

J.H. has MorphOS-Team leave (AFAIK around 2003).
Will /can nobody really from MorphOS-Team evolve SFS (Files >4GiB, Remove 128GiB Bug)?

[ Edited by mk on 2009/1/20 15:11 ]

> We do "weirder" things already, like mounting ISO files as volumes

...which is not as weird as handling volumes as files ;-)

> J.H. has MorphOS-Team leave (AFAIK around 2003).

AFAIK, John Hendrikx had never been member of the MorphOS Team.

well, the problem remains, and so i need to check the integrity of the hdd. is there a tool, that checks the complete hdd (with such sizes like 750 gigs) integrity block by block?

thanks in advance.

bye, MarK.