From: "Ragnar Kjørstad" <kernel@ragnark.vestdata.no>
To: Ben LaHaise <bcrl@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mike@bigstorage.com, kevin@bigstorage.com
Subject: Re: [PATCH] 64 bit scsi read/write
Date: Fri, 10 Aug 2001 21:51:36 +0200 [thread overview]
Message-ID: <20010810215136.C16864@vestdata.no> (raw)
In-Reply-To: <20010703065312.J4841@vestdata.no> <Pine.LNX.4.33.0107032211120.30968-100000@toomuch.toronto.redhat.com> <20010726041821.C19238@vestdata.no>
In-Reply-To: <20010726041821.C19238@vestdata.no>; from Ragnar Kjørstad on Thu, Jul 26, 2001 at 04:18:21AM +0200
On Thu, Jul 26, 2001 at 04:18:21AM +0200, Ragnar Kjørstad wrote:
> On Tue, Jul 03, 2001 at 10:19:36PM -0400, Ben LaHaise wrote:
> > Here's the [completely untested] generic scsi fixup, but I'm told that
> > some controllers will break with it. Give it a whirl and let me know how
> > many pieces you're left holding. =) Please note that msdos partitions do
> > *not* work on devices larger than 2TB, so you'll have to use the scsi disk
> > directly. This patch applies on top of v2.4.6-pre8-largeblock4.diff.
>
> I just trid this, but when I can't load the md modules becuase of
> missing symbols for __divdi3 and __umoddi3.
I compiled md and lvm into the kernel rather than modules and got a
little futher:
* raid 0 over 4*600GB devices:
* made filesystem
* tried reading of the end of the device (dd skip=xx)
all tests successful
* >1TB devices over scsi.
* /proc/partitions report incorrect sizes
[root@K2 /root]# cat /proc/partitions
major minor #blocks name
8 0 17921835 sda
8 1 56196 sda1
8 2 1 sda2
8 5 13076878 sda5
8 6 530113 sda6
8 16 9223372035816620928 sdb
8 32 9223372035975108096 sdc
* mkreiserfs fails: "mkreiserfs: can not create filesystem on that
small device (0 blocks)."
* mkfs.xfs fails: "warning - cannot set blocksize on block device
/dev/sdb: Invalid argument"
I assume both mkreiserfs and mkfs.xfs use ioctl to get the size
of the device, and that ioctl uses an unsigned int? How is
userspace supposed to get the devicesize of >2GB devices with
your code?
* mkfs.ext2 makes the machine panic after a while.
Unfortenately I don't have the panic message anymore, and at the
moment I don't have the hardware to redo the test.
* fdisk bails out with 'Unable to read /dev/sdb'
Strace shows:
open("/dev/sdb", O_RDWR) = 3
uname({sys="Linux", node="K2.torque.com", ...}) = 0
ioctl(3, 0x1268, 0xbffff8f4) = 0
fstat64(3, {st_mode=S_IFBLK|0660, st_rdev=makedev(8, 16), ...}) = 0
ioctl(3, BLKGETSIZE, 0xbffff924) = 0
ioctl(3, HDIO_GETGEO, 0xbffff918) = 0
read(3, "", 512) = 0
--
Ragnar Kjorstad
Big Storage
next prev parent reply other threads:[~2001-08-10 19:51 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-01 4:53 [RFC][PATCH] first cut 64 bit block support Ben LaHaise
2001-07-03 4:53 ` Ragnar Kjørstad
2001-07-04 2:19 ` [PATCH] 64 bit scsi read/write Ben LaHaise
2001-07-04 7:11 ` Alan Cox
2001-07-05 6:34 ` Ragnar Kjørstad
2001-07-05 7:35 ` Ben LaHaise
2001-07-13 18:20 ` Albert D. Cahalan
2001-07-13 20:41 ` Andreas Dilger
2001-07-13 21:07 ` Chris Wedgwood
2001-07-13 22:04 ` Andreas Dilger
2001-07-14 0:49 ` Jonathan Lundell
2001-07-14 12:27 ` Paul Jakma
2001-07-14 14:48 ` Chris Wedgwood
2001-07-14 15:42 ` Paul Jakma
2001-07-14 17:18 ` Chris Wedgwood
2001-07-20 17:03 ` Stephen C. Tweedie
2001-07-16 18:53 ` Andreas Dilger
2001-07-16 19:13 ` Ragnar Kjørstad
2001-07-13 21:14 ` Alan Cox
2001-07-14 3:23 ` Andrew Morton
2001-07-14 8:45 ` Alan Cox
2001-07-14 14:50 ` Chris Wedgwood
2001-07-14 15:41 ` Jonathan Lundell
2001-07-14 17:00 ` Chris Wedgwood
2001-07-14 20:11 ` Daniel Phillips
2001-07-15 1:21 ` Andrew Morton
2001-07-15 1:53 ` Daniel Phillips
2001-07-15 3:36 ` Chris Wedgwood
2001-07-15 6:05 ` John Alvord
2001-07-15 6:07 ` Chris Wedgwood
2001-07-15 13:16 ` Ken Hirsch
2001-07-15 14:50 ` Chris Wedgwood
2001-07-15 22:14 ` Daniel Phillips
2001-07-17 0:31 ` Juan Quintela
2001-07-15 13:44 ` Daniel Phillips
2001-07-15 14:39 ` Chris Wedgwood
2001-07-15 15:06 ` Jonathan Lundell
2001-07-15 15:22 ` Chris Wedgwood
2001-07-15 17:44 ` Jonathan Lundell
2001-07-15 17:47 ` Justin T. Gibbs
2001-07-15 23:14 ` Rod Van Meter
2001-07-16 0:37 ` Jonathan Lundell
2001-07-16 15:11 ` Rod Van Meter
2001-07-16 8:56 ` Chris Wedgwood
2001-07-16 13:19 ` Daniel Phillips
2001-07-15 15:32 ` Alan Cox
2001-07-15 15:33 ` Chris Wedgwood
2001-07-15 16:24 ` Chris Wedgwood
2001-07-16 1:08 ` Albert D. Cahalan
2001-07-16 8:49 ` Chris Wedgwood
2001-07-21 19:18 ` Alexander Griesser
2001-07-22 3:52 ` Albert D. Cahalan
2001-07-23 14:41 ` Daniel Phillips
2001-07-24 4:29 ` Albert D. Cahalan
2001-07-24 11:45 ` Daniel Phillips
2001-07-14 17:33 ` Jonathan Lundell
2001-07-15 4:02 ` Chris Wedgwood
2001-07-15 5:46 ` Jonathan Lundell
2001-07-15 17:10 ` Chris Wedgwood
2001-07-15 17:39 ` Jonathan Lundell
2001-07-26 2:18 ` Ragnar Kjørstad
2001-07-26 16:24 ` Andreas Dilger
2001-08-10 19:42 ` Ben LaHaise
2001-08-10 19:51 ` Ragnar Kjørstad [this message]
2001-08-10 20:02 ` Ben LaHaise
2001-08-11 0:18 ` Steve Lord
2001-08-11 21:44 ` Matti Aarnio
2001-07-04 10:16 ` [RFC][PATCH] first cut 64 bit block support Chris Wedgwood
2001-07-04 16:59 ` Ben LaHaise
-- strict thread matches above, loose matches on Subject: below --
2001-07-14 15:08 [PATCH] 64 bit scsi read/write Ed Tomlinson
2001-07-19 7:35 [PATCH] 64 bit SCSI read/write Andre Hedrick
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=20010810215136.C16864@vestdata.no \
--to=kernel@ragnark.vestdata.no \
--cc=bcrl@redhat.com \
--cc=kevin@bigstorage.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@bigstorage.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox