From: Eric Sandeen <sandeen@sandeen.net>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: nscott@aconex.com, xfs@oss.sgi.com
Subject: Re: mkfs.xfs doesn't detect size of storage correctly
Date: Tue, 29 Jan 2008 09:19:43 -0600 [thread overview]
Message-ID: <479F440F.2060506@sandeen.net> (raw)
In-Reply-To: <20080129122051.GA18165@citd.de>
Matthias Schniedermeyer wrote:
> A maybe important detail, i forgot to mention in the original mail is:
> The machine has 8GB of RAM, so i compiled the kernel with "64bit=yes"
> (formaly x86_64), BUT(!) the userspace is 32bit or plain old i386.
If you think that's the issue, I'd try compiling the above as a 32-bit
binary and re-run.
Although, for a simple sparse-file-backed loopback device w/o loop-aes,
that doesn't cause any problem for me:
[root@inode tmp]# ls -l loopfile
-rw-r--r-- 1 root root 750156369920 2008-01-29 08:53 loopfile
[root@inode tmp]# losetup /dev/loop0 loopfile
[root@inode tmp]# ./gds32 /dev/loop0
1465149160 512 byte blocks (BLKGETSIZE64)
[root@inode tmp]# ./gds64 /dev/loop0
1465149160 512 byte blocks (BLKGETSIZE64)
-Eric
> Bis denn
>
next prev parent reply other threads:[~2008-01-29 15:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-29 9:32 mkfs.xfs doesn't detect size of storage correctly Matthias Schniedermeyer
2008-01-29 10:15 ` nscott
2008-01-29 12:20 ` Matthias Schniedermeyer
2008-01-29 15:19 ` Eric Sandeen [this message]
2008-01-29 15:33 ` Matthias Schniedermeyer
2008-01-29 15:42 ` Eric Sandeen
2008-01-29 16:58 ` Matthias Schniedermeyer
2008-01-29 17:16 ` Matthias Schniedermeyer
2008-01-29 20:14 ` Eric Sandeen
[not found] ` <20080129203731.GA29094@puku.stupidest.org>
2008-01-29 21:21 ` Eric Sandeen
2008-01-30 23:26 ` Matthias Schniedermeyer
2008-01-31 3:17 ` Eric Sandeen
2008-02-05 14:53 ` Eric Sandeen
2008-02-05 15:33 ` Matthias Schniedermeyer
2008-02-05 21:12 ` Mark Goodwin
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=479F440F.2060506@sandeen.net \
--to=sandeen@sandeen.net \
--cc=ms@citd.de \
--cc=nscott@aconex.com \
--cc=xfs@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.