From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: God <atm@sdk.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG?] :: "Value too large for defined data type"
Date: Wed, 15 Aug 2001 12:52:07 +0200 [thread overview]
Message-ID: <20010815125207.E9870@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0108150418230.8270-100000@scotch.homeip.net>
In-Reply-To: <Pine.LNX.4.21.0108150418230.8270-100000@scotch.homeip.net>; from atm@sdk.ca on Wed, Aug 15, 2001 at 04:22:05AM -0400
Hi helpless God, ;-)
On Wed, Aug 15, 2001 at 04:22:05AM -0400, God wrote:
> </mental picture>
>
> ... dump crashed with:
>
> DUMP: 78.80% done at 814 kB/s, finished in 0:10
> DUMP: error reading command pipe in master: No such file or directory
> DUMP: The ENTIRE dump is aborted.
>
> Trying to check where dump should have written the file on box2, I get:
>
> # ls -al
> /bin/ls: test: Value too large for defined data type
> total 2097216
> drwxrwxrwx 2 root root 32768 Aug 14 23:27 ./
> drwxrwxrwx 50 root root 32768 Aug 14 21:02 ../
> -rwxrwxrwx 1 root root 2147483647 Aug 14 22:11
> box1.071401.dump*
> #
Your /bin/ls box2 is not LFS[1] aware. Maybe your dump isn't either?
> Ok so I lied, that is a paste from after my little expriment, but you can
> see the file size. 2.1G, out of a 3G drive.
Looks like LFS problem somewhere.
> It was a stupid thing to do, but could there be a better way for the OS to
> handle this and is there any way I can remove the file? It's on a 60
> Gig drive, so formatting would not be an option right about now ...
Use some rm, which has been compiled for LFS. If your glibc
doesn't support it, then you can only help yourself with some
boot disk with LFS aware tools.
Regards
Ingo Oeser
[1] Large File Support = Support for using large files on a file system
next prev parent reply other threads:[~2001-08-15 10:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 8:22 God
2001-08-15 10:52 ` Ingo Oeser [this message]
2001-08-15 14:04 ` Steve Brueggeman
2001-08-15 15:09 ` Andreas Dilger
2001-08-15 18:28 ` lk
2001-08-15 20:44 ` David Ford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010815125207.E9870@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=atm@sdk.ca \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®