"Value too large to be stored in data type"
FreeBSD rincewind 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #0: Tue Oct 10 13:57:46 PDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ODIN32 i386 I used tar to create several tar files. Then I used growfs from the dvd+rw-tools port to burn them to a dvd. The exact command I used was "growisofs -Z /dev/cd0 -r -J -speed=4 backups/". The disc mounts fine, but: rincewind# cd /cdrom && ls ls: 2006-10-11.all.tar: Value too large to be stored in data type 2006-10-05-apache-config.tar 2006-10-05-ssl.tar 2006-10-11.rincewind.all.sql rincewind# du -hs 2006-10-11.all.tar du: 2006-10-11.all.tar: Value too large to be stored in data type etc... A google search shows someone asking about this error message on -questions before. The only follow ups I saw suggested it was some kind of gnu tar -> bsd tar snafu. These tarballs were created on this very same freebsd and the errors show up with any command, not just tar. My best guess is that it has to do with using Juliet extensions when I burned it. Does anyone have some a definative answer? It is a remote machine so I cannot just pop another dvd in and try with a different set of options. Please CC me. I am not subscribed to -questions. -- luctor et emergo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Value too large to be stored in data type -- gzipped tarball
On 12/18/05, TuxGirl <[EMAIL PROTECTED]> wrote: > > There is nothing wrong with tar and large files, it's synonymous with > > what tar is used for. I think your problem is just a Linux tar to > > FreeBSD tar quirk. I had no problems with the 3.3GB testfile I made > > for tar and gzip to play with: > > I think I may have found some additional info about the problem: > http://groups.google.com/group/list.freebsd.questions/browse_thread/thread/9234a3841dce6209/ce62e532d4e2fa0d?lnk=st&q=%22+Value+too+large+to+be+stored+in+data+type%22+freebsd&rnum=14&hl=en#ce62e532d4e2fa0d > > It appears that the problem has something to do with large files > burned to DVD and read in freebsd (linux has not had a problem with > it, from what I've seen). > > I've found a few articles on google and google-groups regarding this, > but they all seem to be related to burning DVDs in FreeBSD. It > appears to be the same problem however... So, I guess now my question > is, does anybody have any great ideas for getting around this? I was > wondering if it's possible to use dd to copy the tarball over to my > local drivek so that i can work with it that way. I haven't had the > chance yet to figure out dd well enough to know if this is possible or > how I would do it, but it seems to be the best option i've been able > to think of... > > Thanks for the help! > ~Erin > >From what I've read their is a 2GB limit per file on ISO9660 file systems. It seems as though Linux 'worked around' this limit thus forcing you into this problem. dd will not work for you. the only easy workaround is to mount the DVD on a Linux box and then copy the file over the network to the FreeBSD box, or make a new DVD. In the future make sure the files you burn to disc are less then 2GB. dd is for disk image stuff to see what it does and how it works read up on mdconfig and mdmfs (man pages). you want to make file backed (vnode) memory disks to use for playing with dd... http://www.crazytrain.com/dd.html Also grab some floppy, hdd, or even cd image files to play. http://rcsg-gsir.imsb-dsgi.nrc-cnrc.gc.ca/documents/advanced/node13.html http://www.rajeevnet.com/hacks_hints/os_clone/os_cloning.html anyways... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Value too large to be stored in data type -- gzipped tarball
On 12/18/05, TuxGirl <[EMAIL PROTECTED]> wrote: > > > I have a gzipped tarball that I created on my box when i was running > > > Linux, and I burned it, along with some other files, onto a dvd. I'm > > > now trying to extract the tarball, but it appears that it must be over > > > some sort of filesystem limit or something. None of the commands that > > > I have tried seem to like the file. Each of them gives the same > > > > [snip] > > > > > I'm fairly certain that the tarball is fine, because it worked fine on > > > my server last week, when i opened it up there... > > > > Might want try a different implementation of tar then > > cd /usr/ports/archivers; make search name="tar"| more > > I will try this, however, when I mentioned that other commands were > also not playing nicely with the file, I was referring to commands > such as cp, mv, and ls. I'll see if another tar command will work, > though. thanks for the reply! > ~Erin > There is nothing wrong with tar and large files, it's synonymous with what tar is used for. I think your problem is just a Linux tar to FreeBSD tar quirk. I had no problems with the 3.3GB testfile I made for tar and gzip to play with: > uname -a FreeBSD spectra.intranet 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Sun Dec 11 02:56:58 CST 2005 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/Info-Matic i386 > cat /dev/random > testfile > ls -al testfile -rw-r--r-- 1 nbritton nbritton 3526029312 Dec 18 22:12 testfile > md5 testfile MD5 (testfile) = 83e574c15a7daf44f063d140d3577630 > tar -czf testfile.tar.gz testfile > ls -al testfile* -rw-r--r-- 1 nbritton nbritton 3526029312 Dec 18 22:12 testfile -rw-r--r-- 1 nbritton nbritton 3527105097 Dec 18 22:32 testfile.tar.gz > rm testfile; tar -xf testfile.tar.gz; md5 testfile MD5 (testfile) = 83e574c15a7daf44f063d140d3577630 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Value too large to be stored in data type -- gzipped tarball
> > I have a gzipped tarball that I created on my box when i was running > > Linux, and I burned it, along with some other files, onto a dvd. I'm > > now trying to extract the tarball, but it appears that it must be over > > some sort of filesystem limit or something. None of the commands that > > I have tried seem to like the file. Each of them gives the same > > [snip] > > > I'm fairly certain that the tarball is fine, because it worked fine on > > my server last week, when i opened it up there... > > Might want try a different implementation of tar then > cd /usr/ports/archivers; make search name="tar"| more I will try this, however, when I mentioned that other commands were also not playing nicely with the file, I was referring to commands such as cp, mv, and ls. I'll see if another tar command will work, though. thanks for the reply! ~Erin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Value too large to be stored in data type -- gzipped tarball
On 12/18/05, TuxGirl <[EMAIL PROTECTED]> wrote: > I have a gzipped tarball that I created on my box when i was running > Linux, and I burned it, along with some other files, onto a dvd. I'm > now trying to extract the tarball, but it appears that it must be over > some sort of filesystem limit or something. None of the commands that > I have tried seem to like the file. Each of them gives the same [snip] > I'm fairly certain that the tarball is fine, because it worked fine on > my server last week, when i opened it up there... Might want try a different implementation of tar then cd /usr/ports/archivers; make search name="tar"| more ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Value too large to be stored in data type -- gzipped tarball
I have a gzipped tarball that I created on my box when i was running Linux, and I burned it, along with some other files, onto a dvd. I'm now trying to extract the tarball, but it appears that it must be over some sort of filesystem limit or something. None of the commands that I have tried seem to like the file. Each of them gives the same error: /cdrom/music.tgz: Value too large to be stored in data type It doesn't complain about another gzipped tarball on the same disk which is around 1.3 GB, but this one is, I think around 2.4 GB. I've tried copying the file, and tarring it in place, and a number of other things,and I just can't seem to figure out how to resolve the problem. Is there a setting someplace that I can change to make it play nicely with large files? I would think that having a limit on the size of files would cause problems not only with files like this, but also with databases and such, so there must be some way to find the necessary information. Obligatory system info: [amon-re erins] uname -a FreeBSD amon-re 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Thu Nov 3 09:36:13 UTC 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Currently running the default kernel... I'm fairly certain that the tarball is fine, because it worked fine on my server last week, when i opened it up there... Thanks, ~Erin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
