From: Johann Hanne <jhml@gmx.net>
To: Steve McIntyre <steve@einval.com>
Cc: linux-scsi@vger.kernel.org, smcintyre@software.plasmon.com
Subject: Re: Is it possible to support a sector size 8192
Date: Sat, 23 Jul 2005 15:28:20 +0200 [thread overview]
Message-ID: <200507231528.20356.jhml@gmx.net> (raw)
In-Reply-To: <E1Dw26Z-0005m7-JQ@sledge.mossbank.org.uk>
Wow, an answer directly from Plasmon, that's nice. :-)
I've already got the FUSE driver (udofs-1.1-92.i386.rpm, based on FUSE 1.4, is
this current?!). It is nice for a standalone drive, but we use a SCSI robotic
changer in conjunction with an HSM system (Legato DiskXtender 2.9) which
needs some kind of direct access to the drive. It probes for /dev/nst*, but I
guess /dev/sd* would also work.
I know this exact configuration is not officially supported, but I'm a bit
dissapointed that the limiting factor seems to be the Linux kernel. If I
don't find a solution, it will probably become a Solaris/SPARC solution next
week. :-(
Cheers, Johann
On Friday 22 July 2005 20:18, Steve McIntyre wrote:
> Johann wrote:
> >Hi everybody,
> >
> >i'm trying to access UDO/WORM mediums (which have a sector size of
> >8192) via a Plasmon UDO drive, but all I get is "unsupported sector
> >size 8192" when I try to access it via /dev/sdX. drivers/scsi/sd.c
> >suggests that the maximum sector size currently supported by Linux is
> >4096.
> >
> >How difficult will it get to support 8192? Maybe we can pay somebody
> >for doing it? (Kernel 2.4.21, RHEL 3.1).
>
> We (at Plasmon) investigated adding support in the kernel, but gave up
> quickly as it looked like it would need a huge amount of work in
> multiple areas. Instead, we've started shipping a userland filesystem
> driver for UDO based on FUSE. If you'd be interested in that, let me
> know...
next prev parent reply other threads:[~2005-07-23 11:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-22 19:26 Is it possible to support a sector size 8192 Johann Hanne
2005-07-22 18:18 ` Steve McIntyre
2005-07-22 19:21 ` Christian Iversen
2005-07-22 21:21 ` Bryan Henderson
2005-07-23 13:31 ` Johann Hanne
2005-07-23 18:29 ` Steve McIntyre
2005-07-23 13:28 ` Johann Hanne [this message]
2005-07-23 18:56 ` Steve McIntyre
2005-07-25 15:43 ` Jay Denebeim
2005-07-25 19:08 ` Steve McIntyre
2005-07-25 19:37 ` Jay Denebeim
2005-07-25 20:49 ` Steve McIntyre
2005-07-25 22:38 ` Johann Hanne
2005-07-25 20:50 ` Steve McIntyre
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=200507231528.20356.jhml@gmx.net \
--to=jhml@gmx.net \
--cc=linux-scsi@vger.kernel.org \
--cc=smcintyre@software.plasmon.com \
--cc=steve@einval.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