public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Schmid <webmaster@rapidforum.com>
To: linux-kernel@vger.kernel.org
Subject: Large Block Devices not supported in 64 bit
Date: Wed, 06 Sep 2006 17:12:20 +0200	[thread overview]
Message-ID: <44FEE554.5050903@rapidforum.com> (raw)

Hello.

I run kernel 2.6.17.11 vanilla in 64 bit mode with 32 bit emulation.

Unfortunately there is no support for file-systems bigger than 2 TB in 64 bit mode.

erikm in #kernelnewbies told me to report it here:

<Dragony> statfs("/MD2", 0xff8deca4)              = -1 EOVERFLOW (Value too large for defined data type)
<erikm> Dragony: prolly no LBD support
<erikm> Dragony: ah wait, you probably do have support for large block devices, but the 32 bit 
portability syscall forgot to support it
<erikm> Dragony: see block/Kconfig
<Dragony> #XXX - it makes sense to enable this only for 32-bit subarch's, not for x86_64
<Dragony> #for instance.
<Dragony> config LBD
<Dragony>         bool "Support for Large Block Devices"
<Dragony>         depends on X86 || (MIPS && 32BIT) || PPC32 || (S390 && !64BIT) || SUPERH || UML
<Dragony> yes but this option only appears in 32 bit mode not in 64 bit mode
<erikm> Dragony: hence my comment
<Dragony> actually /MD2 is mounted and i can access the files, but not any stats
<erikm> Dragony: it *IS* supported, but not properly backported to the 32 bit compatibility layer
<Dragony> hmm what can i do?
<erikm> Dragony: post to lkml

Can someone help me?

Regards,
Chris

             reply	other threads:[~2006-09-06 15:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-06 15:12 Christian Schmid [this message]
2006-09-08 10:45 ` Large Block Devices not supported in 64 bit Chris Boot

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=44FEE554.5050903@rapidforum.com \
    --to=webmaster@rapidforum.com \
    --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