All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Greaves <david@dgreaves.com>
To: Neil Brown <neilb@suse.de>
Cc: Martin Filip <bugtraq@smoula.net>, linux-kernel@vger.kernel.org
Subject: Re: NFS and partitioned md
Date: Tue, 18 Jul 2006 19:36:25 +0100	[thread overview]
Message-ID: <44BD2A29.8060405@dgreaves.com> (raw)
In-Reply-To: <17571.19699.980491.970386@cse.unsw.edu.au>

Neil Brown wrote:
> On Tuesday June 27, bugtraq@smoula.net wrote:
>> Hi,
>>
>> thx for your interrest,
>>
>> Neil Brown píše v Út 27. 06. 2006 v 10:32 +1000:
>>> So I suspect there is something else going on that has nothing to do
>>> with the usage of partitioned md.... then again, maybe there is some
>>> weird sign extension happening to '254' somewhere, though that would
>>> be terribly strange.
>> (as I look on that it comes on my mind, that problem could be minor
>> longer than 1 byte)
>>
> 
> Exactly.  4105 > 256.  Such devices need a different format filehandle
> which didn't work until very recently due to a bug (obviously no-one
> tried it until recently).
> 
> The patch below fixes the kernel so that this will work.
> Alternately use md_d0 md_d1, md_d2, or md_d3.  Then it will work with
> no patches.

FWIW (and google) I have just encountered this problem on 2.6.16.9 server.

My error message with the NFS mount failing was:
mount teak:/media /mnt/test
mount: teak:/media: can't read superblock

teak:~# ll /dev/media*
brw-rw---- 1 root disk 254, 8128 2006-07-18 18:39 /dev/media
brw-rw---- 1 root disk 254, 8129 2006-07-18 18:39 /dev/media1
brw-rw---- 1 root disk 254, 8130 2006-07-18 18:39 /dev/media2
brw-rw---- 1 root disk 254, 8131 2006-07-18 18:39 /dev/media3
brw-rw---- 1 root disk 254, 8132 2006-07-18 18:39 /dev/media4

I rebooted to use /dev/md_d0 and /dev/md_d0p1 and it's fine.

David

  parent reply	other threads:[~2006-07-18 18:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26 20:52 NFS and partitioned md Martin Filip
2006-06-26 20:58 ` Trond Myklebust
2006-06-26 21:21   ` Martin Filip
     [not found]   ` <1151356840.4460.18.camel@archon.smoula-in.net>
2006-06-26 21:51     ` Trond Myklebust
2006-06-26 22:14       ` Martin Filip
2006-06-26 22:32         ` Trond Myklebust
2006-06-27  0:32 ` Neil Brown
2006-06-27 18:18   ` Martin Filip
2006-06-29  3:45     ` Neil Brown
2006-06-29 16:01       ` Martin Filip
2006-07-18 18:36       ` David Greaves [this message]
2006-07-18 20:04         ` Martin Filip
2006-07-20  0:30           ` Neil Brown
2006-07-20  9:07             ` Frank van Maarseveen
2006-07-20  9:07               ` Frank van Maarseveen
2006-08-21  2:29               ` Neil Brown
2006-08-21  2:29                 ` [NFS] " Neil Brown

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=44BD2A29.8060405@dgreaves.com \
    --to=david@dgreaves.com \
    --cc=bugtraq@smoula.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    /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.