From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932377AbWGRUFK (ORCPT ); Tue, 18 Jul 2006 16:05:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932380AbWGRUFK (ORCPT ); Tue, 18 Jul 2006 16:05:10 -0400 Received: from r16s03p19.home.nbox.cz ([83.240.22.12]:42678 "EHLO scarab.smoula.net") by vger.kernel.org with ESMTP id S932377AbWGRUFI (ORCPT ); Tue, 18 Jul 2006 16:05:08 -0400 Subject: Re: NFS and partitioned md From: Martin Filip To: David Greaves Cc: Neil Brown , linux-kernel@vger.kernel.org In-Reply-To: <44BD2A29.8060405@dgreaves.com> References: <1151355145.4460.16.camel@archon.smoula-in.net> <17568.31894.207153.563590@cse.unsw.edu.au> <1151432312.11996.32.camel@reaver.netbox-in.cz> <17571.19699.980491.970386@cse.unsw.edu.au> <44BD2A29.8060405@dgreaves.com> Content-Type: text/plain; charset=ISO-8859-2 Date: Tue, 18 Jul 2006 22:04:59 +0200 Message-Id: <1153253099.26360.3.camel@archon.smoula-in.net> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, my solution was to use fsid parameter for exports... maybe some other mechanism for selecting fsids could be created instead of fsid = device minor nx David Greaves píše v Út 18. 07. 2006 v 19:36 +0100: > 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