Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Greg Russell Newsgroups: comp.os.linux.misc Subject: Re: ext3 filesize problem Date: 4 Feb 2012 07:14:32 GMT Lines: 56 Message-ID: <9p446nFok3U2@mid.individual.net> References: <9o11esFnm1U1@mid.individual.net> <9p2rf0F4v8U1@mid.individual.net> <9p3r5nF7s6U1@mid.individual.net> <9p3tnaFok3U1@mid.individual.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net OCHjL71HrA8hKa260gOBqgrcXVKLlu615ZLF+FUdbQbs0JwXFW Cancel-Lock: sha1:lUAq5XKe5O7lSNr1B4yATmxAv4E= User-Agent: Pan/0.133 (House of Butterflies) Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.misc:4098 On Sat, 04 Feb 2012 06:57:04 +0100, Aragorn wrote in jgihbg$dov$1@dont-email.me : > On Saturday 04 February 2012 06:23, Greg Russell conveyed the following > to comp.os.linux.misc... > >> On Sat, 04 Feb 2012 05:47:06 +0100, Aragorn wrote in >> jgid8b$vrm$1@dont-email.me : >> >>> On Saturday 04 February 2012 05:40, Greg Russell conveyed the >>> following to comp.os.linux.misc... >>> >>>> On Fri, 03 Feb 2012 20:55:59 +0000, J G Miller wrote in >>>> jghhkv$on1$1@dont-email.me : >>>> >>>>> On Friday, February 3rd, 2012, at 19:39:13h +0000, Greg Russell >>>>> wrote: >>>>> >>>>>> but why motion should limit an mpeg file to 2GB is still not >>>>>> understandable to me >>>>> >>>>> Well in another post, Stan has suggested the reason is due to the 32 >>>>> bit limit if you are using a 32 bit version of motion. >>>> >>>> Yes, ... and I find that reasoning to be inadequate and unconvincing. >>>> 2 GB is not a limit on a 32-bit ext3 filesystem. >>> >>> No, but it may be and often is the limit of /certain/ 32-bit >>> _applications_ [*]. It has nothing to do with the ext3 filesystem. >>> >>> >>> [*] The following pertains to web browsers and download utilities, >>> but it's a useful bit of information...: >>> http://www.kernel.org/faq/#largefiles >> >> No, it's not useful at all in explaining why motion limits itself to a >> 2GB output filesize on a filesystem that isn't 2GB-limited; it has no >> relation to the topic under discussion. > > It explains why certain applications are known to limit the size of a > downloaded file to 2 GB ... No, it certainly doesn't. > Apparently "motion" - or at least, the 32-bit version of it - cannot > handle files larger than 2 GB. Buffer size, checkpoints, et al. It is > not - repeat: not - a limitation of the filesystem, but instead it is a > limitation of the application. ... good, good, you're starting to address the issue, albeit quite obliquely. > There are editors which suffer from the same limitation. ... ... and what limitation is that wrt "motion"?