<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jan 20, 2008, at 7:46 AM, Kevin Kuphal wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Jan 20, 2008 8:06 AM, William Munson <<a href="mailto:w.munson@comcast.net">w.munson@comcast.net</a>> wrote:<br> <blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"> <div> <div></div> <div class="Wj3C7c">Phill Edwards wrote:<br>> In order to make it easier to install CentOS I am going to reformat my<br>> JFS file system which stores my recordings to EXT3. It's a 320GB IDE<br>> disk. The archives have lots of file system discussions but I can't <br>> find anything which says what block size to format the EXT3 partition<br>> with for storing large files like recordings. Can anybody advise?</div></div></blockquote> <div> </div> <div>Just a note, I've been using JFS for a *long* time without issues. Last I heard though XFS had issues when the drives got full and Myth usually runs in a disk full scenario...</div></div></blockquote><div><br class="webkit-block-placeholder"></div><div>The only issue I had with full drives was fragmentation. Setting allocsize=512m in the mount options fixed it.</div><div><br class="webkit-block-placeholder"></div><div>There are known issues with XFS in kernels with 4K stacks. The problem crops up when you stack up too many filesystem layers, so it usually shows up in LVM+RAID+XFS setups. In theory this is fixable, but I don't know if anyone's fixed it.</div><div><br class="webkit-block-placeholder"></div></div></body></html>