|
Re: e2fsck problem: (Bad address) while doing inode scan: msg#00217lib.uclibc.general
On Mon Mar 31, 2003 at 05:41:12PM +0200, Giulio Orsero wrote: > On Fri, 28 Mar 2003 19:58:44 +0100, Giulio Orsero <giulioo@xxxxxxxxx> wrote: > > >Right now I don't have a real system (as opposed to vmware) to test it. If > >necessary will do it next days. > > Following is data on real hardware (previous was on vmware): > > hda4 is about 9GB [--------snip----------] > _llseek(3, 4294967296, 0x9febfc00, SEEK_SET) = -1 EFAULT (Bad address) Ok. So you have a 9 GB drive. And you try to seek past 4 GB with a kernel that does not have large file support, and the kernel is responding by telling you it can't do that. This doesn't look like a uClibc problem to me, -Erik -- Erik B. Andersen http://codepoet-consulting.com/ --This message was written using 73% post-consumer electrons-- |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: small one liner patch: 00217, Erik Andersen |
|---|---|
| Next by Date: | Re: e2fsck problem: (Bad address) while doing inode scan: 00217, Giulio Orsero |
| Previous by Thread: | Re: e2fsck problem: (Bad address) while doing inode scani: 00217, Giulio Orsero |
| Next by Thread: | Re: e2fsck problem: (Bad address) while doing inode scan: 00217, Giulio Orsero |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |