|
Hardware Support Discussions related to using various hardware setups with SageTV products. Anything relating to capture cards, remotes, infrared receivers/transmitters, system compatibility or other hardware related problems or suggestions should be posted here. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
How important is 64K block size
Can anyone explain to me how important 64K block size is for recording or playing back HD material.
I have numerous 250gig disks (a total of six) on my HD Sage setup and just realized that they are all formated with 4K disk block / sector size. The system works quite well with only ocasional stuttering. Fixing this issue (changing to 64K block size) will be a real pain. Comments? |
#2
|
||||
|
||||
I believe it to be very important. My understanding is that once the file is fragmented on the 4K cluster size, it can become impossible for the drive to seek to the next file portion faster enough to keep up with the data throughput needed for recording or playback (and that's just for SD material), so there will be data lost while trying to record or stuttering during playback. This is usually not an issue with 64K clusters - I won't say it is impossible for fragmentation to be an issue with 64K clusters, but it is much less likely. I haven't defragged my recording drives in over a year & don't plan to do so.
There are utilities that can change the cluster size w/o reformatting. Partition Magic can do it & so can a utility from Acronis, among possible others. Lately, I would go with Acronis. - Andy
__________________
SageTV Open Source v9 is available. - Read the SageTV FAQ. Older PDF User's Guides mostly still apply: SageTV V7.0 & SageTV Studio v7.1. - Hauppauge remote help: 1) Basics/Extending it 2) Replace it 3) Use it w/o needing focus - HD Extenders: A) FAQs B) URC MX-700 remote setup Note: This is a users' forum; see the Rules. For official tech support fill out a Support Request. |
#3
|
|||
|
|||
Agree with Opus, but from past experience...if it ain't broke, don't fix it.
|
#4
|
|||
|
|||
Quote:
When I did this I just copied all of my content off to another drive and re-formatted to 64k, then copied it back (directory structure and all). He said there were numerous drives, so finding space should not be too much of a problem. Or delete temporary shows (after watching them stuttering) and delete. Then reformat. Mike
__________________
Athlon64 3200+ 2.0GHz, 1GB RAM, XP Home, 200GB and 300GB Barracuda HDs, Toshiba DVD/RW DL, eVGA GeForce 6600 256MB TV/HD-DVI out, WinTV-PVR-500 MCE, WinTV-PVR-150 MCE, USB UIRT + remote, XGene wireless KBD, Panasonic TH42PX60U HDTV, SA-8300HD STB on Time Warner Expanded Digital Cable San Diego, JVC receiver, Energy Take2.5 surround sound, Sony DVD player |
#5
|
|||
|
|||
Oops, missed that, sorry.
|
#6
|
|||
|
|||
64k
curiuos, if 64k is that much better why isnt it the default? woudnt it be better to run all computers for any application with this cluster size?
|
#7
|
|||
|
|||
Quote:
B |
#8
|
|||
|
|||
Quote:
Say you have a 1k file. If your drive is formated to 4k it's going to take up 4k of space. On a disk formated to 64k that same file is going to take up 64k. Regardless of the file size it's going to be stored in a multiple of 4 k, 64k, or whatever the drive is formated to. So if the file was 65k it would take up 68k or 128k. It's impossible for 64k to become as fragemented as 4k can get. |
#9
|
||||
|
||||
Quote:
Thanks to PM a few yrs ago I lost an 18gig data drive (back when that was a big deal) while trying to merge 2 volumes w/ differing cluster sizes. PM tried to rework one of them to match and failed miserably. Best I managed to recover was a listing of the filenames on the partition. Least I know what I HAD. YMMV
__________________
Server: MS Win7 SP1; FX8350 (H2O cooled); 8GB RAM; Hauppauge HVR-7164 (OTA); HVR-885 (OTA); SageTV 9.1.5.x; 12+TB Sage Storage Clients: HD300 x2; HD200 x2; Placeshifter Service: EPB Fiber (1Gb); OTA (we "cut the cord"); Netflix, Hulu, etc. |
#10
|
|||
|
|||
block size
I'm finally getting around to changing the block size on one of my HD's.
I've previously used a 64k block size one one HD, but now running Paragon Disk Manager, I have the option of moving to 128k. Has anybody had any experience with 128k? Is it any better / worse than 64k? |
#11
|
||||
|
||||
Quote:
|
#12
|
|||
|
|||
Neither did I. This is on a 1.5TB disk...maybe size matters?
Anyway, the 128k scared me, so I just stuck with 64k (since I already had recordings on the drive, and didn't want to mess 'em up. otherwise, I would have experimented!) |
#13
|
||||
|
||||
Fat and Fat32 support up to 256k clusters, but I can't find anything that says NTFS supports larger than 64k.
|
#14
|
|||
|
|||
Size always matters!
Sorry I couldn't help it.
__________________
Sage Server: AMD Athlon II 630, Asrock 785G motherboard, 3GB of RAM, 500GB OS HD in RAID 1 and 2 - 750GB Recording Drives, HDHomerun, Avermedia HD Duet & 2-HDPVRs, and 9.0TB storage in RAID 5 via Dell Perc 5i for DVD storage Source: Clear QAM and OTA for locals, 2-DishNetwork VIP211's Clients: 2 Sage HD300's, 2 Sage HD200's, 2 Sage HD100's, 1 MediaMVP, and 1 Placeshifter |
#15
|
|||
|
|||
Probably a stupid question but here goes...
Any way to check in windows xp how a hard drive was formatted? I can't remember if I did or not. |
#16
|
|||
|
|||
Quote:
Greg |
#17
|
||||
|
||||
chdksk.exe will tell you.
|
#18
|
|||
|
|||
See setup below, I've got all kinds of HD flying all over the place and not a 64k cluster in sight, never had any issues.
__________________
Server: WMC Windows 7 64bit, SSD+2TB, Gigabyte 870G, AMD X6, 4GB DDR, ATi 5570 Capture Devices: HDHomeRun (OTA), 2x HD-PVR w/HTTP Tuning (DirecTV H21's) NAS: Windows Home Server: Supermicro C2SBX, C2D 2.6Ghz, 4GB DDR, 32.07TB |
#19
|
|||
|
|||
Also, I think the I/O's per second reduces with the use of 64K blocks for large files.
|
#20
|
||||
|
||||
Yes, hard drives have buffers, which can help smooth out occasional hiccups. But if a file is fragmented to the point where the average fragment contains fewer milliseconds of video than the average seek time between fragments, then buffering can't make up the difference (short of buffering the entire file, and no drive has a buffer that big). That's the point of large clusters: to keep the fragment size well above that seek-time threshold, no matter how fragmented the file gets.
__________________
-- Greg |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|