As we've been playing with Broadcast 2000 on SuSE 7.0 over the weekend, we discovered we needed to make files over 2Gb in size. We couldn't get this going. We'd upgraded to kernel 2.4.2 already, but apparently it also needs a glibc 2.2 built against kernel 2.4, and that proved beyond us (we ended up nuking the machine after trying to install a Red Hat glibc2.2.x - not my idea, but we ended up doing that when glibc2.2.2, the current release, can't be compiled by gcc 2.95.2 - again the current release and the one in suse 7.0) So, any more information on how it can be done and - importantly, as mine should be arriving imminently - does SuSE 7.1 handle large files out of the box? -- Rachel
Rachel Greenham wrote:
As we've been playing with Broadcast 2000 on SuSE 7.0 over the weekend, we discovered we needed to make files over 2Gb in size. We couldn't get this going.
We'd upgraded to kernel 2.4.2 already, but apparently it also needs a glibc 2.2 built against kernel 2.4, and that proved beyond us (we ended up nuking the machine after trying to install a Red Hat glibc2.2.x - not my idea, but we ended up doing that when glibc2.2.2, the current release, can't be compiled by gcc 2.95.2 - again the current release and the one in suse 7.0)
So, any more information on how it can be done and - importantly, as mine should be arriving imminently - does SuSE 7.1 handle large files out of the box?
SuSE Linux 7.0 can handle large files just fine. The problem is the application, it has to actually USE those new glibc calls. 7.1 has many more apps than 7.0 that have been made LFS aware - we just don't have a list which ones ;-( bc2000 is unlikely to have been changed, it's not used that often...
Michael Hasenstein wrote:
Rachel Greenham wrote:
As we've been playing with Broadcast 2000 on SuSE 7.0 over the weekend, we discovered we needed to make files over 2Gb in size. We couldn't get this going.
We'd upgraded to kernel 2.4.2 already, but apparently it also needs a glibc 2.2 built against kernel 2.4, and that proved beyond us (we ended up nuking the machine after trying to install a Red Hat glibc2.2.x - not my idea, but we ended up doing that when glibc2.2.2, the current release, can't be compiled by gcc 2.95.2 - again the current release and the one in suse 7.0)
So, any more information on how it can be done and - importantly, as mine should be arriving imminently - does SuSE 7.1 handle large files out of the box?
SuSE Linux 7.0 can handle large files just fine. The problem is the application, it has to actually USE those new glibc calls. 7.1 has many more apps than 7.0 that have been made LFS aware - we just don't have a list which ones ;-(
bcast2000 certainly is LFS aware. If the SuSE package isn't, the one we built from source certainly is. But we couldn't create any files greater than 2Gb. I'm still hopeful that 7.1, being glibc2.2.x-based, will resolve this though. ... *when* it arrives. I ordered it from the UK office and it *said* a turnaround period of a day or two, but it's been over a week. -- Rachel
Rachel Greenham wrote:
bcast2000 certainly is LFS aware. If the SuSE package isn't, the one we built from source certainly is. But we couldn't create any files greater than 2Gb.
I'm still hopeful that 7.1, being glibc2.2.x-based, will resolve this though.
... *when* it arrives. I ordered it from the UK office and it *said* a turnaround period of a day or two, but it's been over a week.
reiserfs in the 2.2 kernel is NOT lfs-able, by the way...
At 07:44 AM 2/28/2001 -0800, you wrote:
reiserfs in the 2.2 kernel is NOT lfs-able, by the way...
Would you please define "lfs-able" ? Are you saying that it somehow breaks LFS compliance, or are you just saying that there's no specifications for it? ---------------------------------------------------- Jonathan Wilson System Administrator Cedar Creek Software http://www.cedarcreeksoftware.com Central Texas IT http://www.centraltexasit.com
Jonathan Wilson wrote:
At 07:44 AM 2/28/2001 -0800, you wrote:
reiserfs in the 2.2 kernel is NOT lfs-able, by the way...
Would you please define "lfs-able" ? Are you saying that it somehow breaks LFS compliance, or are you just saying that there's no specifications for it?
It doesn't support it. The file system has to support it as well, not just the glibc and the rest of the kernel (the vfs layer).
* Jonathan Wilson [Wed, 28 Feb 2001 09:59:40 -0600]:
Would you please define "lfs-able" ? Are you saying that it somehow breaks LFS compliance, or are you just saying that there's no specifications for it?
reiserFS 3.5.X as used in kernel 2.2 doesn't support files > 2GB, it's that simple :) reiserFS 3.6.X as it's in kernel 2.4.2 does support those but there is one grave caveat: if you either create fresh 3.6 partitions or convert 3.5 to 3.6, you won't be able to install or update your system from a SuSE Linux 7.1 CD and you can't use the rescue disk from the CD. This because 7.1 uses kernel 2.2 in all boot images and thus can't handle reiserFS 3.6 partitions. As SuSE Linux 7.2 will most probably use kernel 2.4 by default, this problem will vanish. -- Penguins to save the dinosaurs -- Handelsblatt on Linux for S/390
On Thu, 1 Mar 2001, Philipp Thomas wrote:
if you either create fresh 3.6 partitions or convert 3.5 to 3.6, you won't be able to install or update your system from a SuSE Linux 7.1 CD and you can't use the rescue disk from the CD. This because 7.1 uses kernel 2.2 in all boot images and thus can't handle reiserFS 3.6 partitions.
As SuSE Linux 7.2 will most probably use kernel 2.4 by default, this problem will vanish.
The above is a show stopper if one wants to run ReiserFS so it looks like I'll wait until 7.2 to upgrade. But by then I'll probably be running Mac OS X on the desktop and continuing with OpenBSD on the server. Greg http://www.2fortheroad.net
* Greg Thomas [Wed, 28 Feb 2001 20:17:30 -0800 (PST)]:
The above is a show stopper if one wants to run ReiserFS so it looks like I'll wait until 7.2 to upgrade.
No, it's not a show stopper, at least if you don't need files >2GB. The mkreiserfs in 7.1 will create 3.5 format partitions, which reiserFS 3.6 will recognise and work with. You'll only lack the support for large files. And when 7.2 is out, you just mount the reiserFS partitions with the conv option and they'll get converted to the new format. -- Penguins to save the dinosaurs -- Handelsblatt on Linux for S/390
Philipp Thomas wrote:
* Jonathan Wilson [Wed, 28 Feb 2001 09:59:40 -0600]:
Would you please define "lfs-able" ? Are you saying that it somehow breaks LFS compliance, or are you just saying that there's no specifications for it?
reiserFS 3.5.X as used in kernel 2.2 doesn't support files > 2GB, it's that simple :) reiserFS 3.6.X as it's in kernel 2.4.2 does support those but there is one grave caveat:
if you either create fresh 3.6 partitions or convert 3.5 to 3.6, you won't be able to install or update your system from a SuSE Linux 7.1 CD and you can't use the rescue disk from the CD. This because 7.1 uses kernel 2.2 in all boot images and thus can't handle reiserFS 3.6 partitions.
This means you cannot boot from CD / disk to update / install doesn't it? I mean if I upgrade to 3.6 and boot my 2.4.x kernel I should be able to install from CD. Otherwise that >2GB thing would be useless. In the "old" times, there used to be three disks: The boot, the root and the yast disk. Furthermore, there was also a rescue disk. Is there any chance to recreate these and offer them for d/l to solve that problem? Granted, no yast2 with these, but if there is a chance to rescue my reiser 3.6... Btw, my problem with gramofile might be caused by reiser 3.5 as well... Juergen
As SuSE Linux 7.2 will most probably use kernel 2.4 by default, this problem will vanish.
-- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\
* juergen.braukmann@ruhr-west.de [Thu, 01 Mar 2001 16:10:53 +0100]:
This means you cannot boot from CD / disk to update / install doesn't it?
Yepp, exactly that.
I mean if I upgrade to 3.6 and boot my 2.4.x kernel I should be able to install from CD. Otherwise that >2GB thing would be useless.
Of cause that'll work. But you can't do a system update from YaST1/YaST2 as it'll refuse to update the base system. So you'd have to update manually.
In the "old" times, there used to be three disks: The boot, the root and the yast disk. Furthermore, there was also a rescue disk.
But the rescue floppy was libc5 based.
Is there any chance to recreate these and offer them for d/l to solve that problem?
I'll ask, but I'm not in a position to actually decide.
Btw, my problem with gramofile might be caused by reiser 3.5 as well...
Could well be. I haven't yet had time to check if gramofile does support LFS. If it does, reiserFS 3.5 would be the limiting factor. -- Penguins to save the dinosaurs -- Handelsblatt on Linux for S/390
Michael Hasenstein wrote:
Rachel Greenham wrote:
bcast2000 certainly is LFS aware. If the SuSE package isn't, the one we built from source certainly is. But we couldn't create any files greater than 2Gb.
I'm still hopeful that 7.1, being glibc2.2.x-based, will resolve this though.
... *when* it arrives. I ordered it from the UK office and it *said* a turnaround period of a day or two, but it's been over a week.
reiserfs in the 2.2 kernel is NOT lfs-able, by the way...
Of course not, we compiled it into a 2.4.2 kernel. -- Rachel
Michael Hasenstein wrote:
Rachel Greenham wrote:
As we've been playing with Broadcast 2000 on SuSE 7.0 over the weekend, we discovered we needed to make files over 2Gb in size. We couldn't get this going.
We'd upgraded to kernel 2.4.2 already, but apparently it also needs a glibc 2.2 built against kernel 2.4, and that proved beyond us (we ended up nuking the machine after trying to install a Red Hat glibc2.2.x - not my idea, but we ended up doing that when glibc2.2.2, the current release, can't be compiled by gcc 2.95.2 - again the current release and the one in suse 7.0)
So, any more information on how it can be done and - importantly, as mine should be arriving imminently - does SuSE 7.1 handle large files out of the box?
SuSE Linux 7.0 can handle large files just fine. The problem is the application, it has to actually USE those new glibc calls. 7.1 has many more apps than 7.0 that have been made LFS aware - we just don't have a list which ones ;-( bc2000 is unlikely to have been changed, it's not used that often...
OK, we're having real problems with this. Can you give me an example of one application in particular that is LFS-aware in 7.0 and/or 7.1? eg: what would happen if I were to dd the SuSE 7.x DVD onto a file or otherwise tarball the entire contents of all the SuSE CD-ROMs? I'd like at least to see *something* produce large files so we know better where the problem is - whether it's with our LFS-aware build of bc2000 or not. Our problem is: We understand that large file support must not only be built into the kernel (2.4.x) but glibc must be built *against* that kernel, or at least that kernel's headers. Such a glibc won't function with a 2.2 kernel (this information is coming directly from kernel developers and borne out by our own experience), yet SuSE allows switching between 2.2 and 2.4 kernels with relative ease; we cannot understand how this *can* work. So I'd really like to see some evidence that it does. :-) Oh, and my 7.1 order arrived today so I'll be playing with that... -- Rachel
Rachel Greenham wrote:
SuSE Linux 7.0 can handle large files just fine. The problem is the application, it has to actually USE those new glibc calls. 7.1 has many more apps than 7.0 that have been made LFS aware - we just don't have a list which ones ;-( bc2000 is unlikely to have been changed, it's not used that often...
OK, we're having real problems with this. Can you give me an example of one application in particular that is LFS-aware in 7.0 and/or 7.1? eg:
dd apache cpio dump file fileutils findutils gawk gzip less perl rsync sh-utils tar wget ... most only since 7.1
what would happen if I were to dd the SuSE 7.x DVD onto a file or otherwise tarball the entire contents of all the SuSE CD-ROMs? I'd like at least to see *something* produce large files so we know better where
dd if=/dev/zero of=file bs=1024 count=(number of kbytes)
the problem is - whether it's with our LFS-aware build of bc2000 or not.
Our problem is: We understand that large file support must not only be built into the kernel (2.4.x) but glibc must be built *against* that kernel, or at least that kernel's headers. Such a glibc won't function with a 2.2 kernel (this information is coming directly from kernel developers and borne out by our own experience), yet SuSE allows
It will with SuSE kernels.
switching between 2.2 and 2.4 kernels with relative ease; we cannot understand how this *can* work. So I'd really like to see some evidence that it does. :-)
Because we do kernel development and backport all the interesting things.
Oh, and my 7.1 order arrived today so I'll be playing with that...
Michael Hasenstein wrote:
Rachel Greenham wrote:
SuSE Linux 7.0 can handle large files just fine. The problem is the application, it has to actually USE those new glibc calls. 7.1 has many more apps than 7.0 that have been made LFS aware - we just don't have a list which ones ;-( bc2000 is unlikely to have been changed, it's not used that often...
OK, we're having real problems with this. Can you give me an example of one application in particular that is LFS-aware in 7.0 and/or 7.1? eg:
dd apache cpio dump file fileutils findutils gawk gzip less perl rsync sh-utils tar wget ...
most only since 7.1
Just to update: Large files work fine on 7.1, including on bc2000 - never did get it going on 7.0 but don't care any more. :-) BTW, just like to add, in case no-one's said it yet, that SuSE 7.1 rocks! :-) -- Rachel
Hi, On Mon, 26 Feb 2001, Rachel Greenham wrote:
As we've been playing with Broadcast 2000 on SuSE 7.0 over the weekend, we discovered we needed to make files over 2Gb in size. We couldn't get this going.
So it seems like bcast2k is not LFS ready yet.
We'd upgraded to kernel 2.4.2 already, but apparently it also needs a glibc 2.2 built against kernel 2.4, and that proved beyond us (we ended up nuking the machine after trying to install a Red Hat glibc2.2.x - not my idea, but we ended up doing that when glibc2.2.2, the current release, can't be compiled by gcc 2.95.2 - again the current release and the one in suse 7.0)
So, any more information on how it can be done and - importantly, as mine should be arriving imminently - does SuSE 7.1 handle large files out of the box?
The base system does. However, the apps need to support is as well, and we are busy working on enabling LFS on as much applications as possible. But I fear, that bcast2k has not been fixed yet... Also have a look at Andreas Jaeger's LFS page: http://www.suse.de/~aj/linux_lfs.html Bye, LenZ -- ------------------------------------------------------------------ Lenz Grimmer SuSE GmbH mailto:grimmer@suse.de Schanzaeckerstr. 10 http://www.suse.de/~grimmer/ 90443 Nuernberg, Germany Tell no big lies today. Small ones are just as effective
Lenz Grimmer wrote:
Hi,
On Mon, 26 Feb 2001, Rachel Greenham wrote:
As we've been playing with Broadcast 2000 on SuSE 7.0 over the weekend, we discovered we needed to make files over 2Gb in size. We couldn't get this going.
So it seems like bcast2k is not LFS ready yet.
same is true with gramofile. After I removed the standard 100 min limit, it ceised after 3h 14 min or 2GB. ;-( Juergen
We'd upgraded to kernel 2.4.2 already, but apparently it also needs a glibc 2.2 built against kernel 2.4, and that proved beyond us (we ended up nuking the machine after trying to install a Red Hat glibc2.2.x - not my idea, but we ended up doing that when glibc2.2.2, the current release, can't be compiled by gcc 2.95.2 - again the current release and the one in suse 7.0)
So, any more information on how it can be done and - importantly, as mine should be arriving imminently - does SuSE 7.1 handle large files out of the box?
The base system does. However, the apps need to support is as well, and we are busy working on enabling LFS on as much applications as possible. But I fear, that bcast2k has not been fixed yet...
Also have a look at Andreas Jaeger's LFS page:
http://www.suse.de/~aj/linux_lfs.html
Bye, LenZ
-- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\
* juergen.braukmann@ruhr-west.de [Wed, 28 Feb 2001 11:06:14 +0100]:
same is true with gramofile. After I removed the standard 100 min limit, it ceised after 3h 14 min or 2GB. ;-(
Thanks for that info ;-) I'll try and see what I can come up, as it was me who brought gramofile into SuSE Linux. Shouldn't be that hard to fix gramofile though. Just some autoconf tests for LFS support and then a few changes in the code. stay tuned .... -- Penguins to save the dinosaurs -- Handelsblatt on Linux for S/390
participants (8)
-
Greg Thomas -
juergen.braukmann＠ruhr-west.de -
Lenz Grimmer -
Michael Hasenstein -
Philipp Thomas -
Philipp Thomas -
Rachel Greenham -
wilson＠claborn.net