Received: with ECARTIS (v1.0.0; list xfs); Tue, 04 Jul 2006 18:37:49 -0700 (PDT) Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id k651bCDW007823 for ; Tue, 4 Jul 2006 18:37:24 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id LAA15000; Wed, 5 Jul 2006 11:36:33 +1000 Received: from wobbly.melbourne.sgi.com (localhost [127.0.0.1]) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id k651aTgw1526234; Wed, 5 Jul 2006 11:36:30 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id k651aOII1524571; Wed, 5 Jul 2006 11:36:24 +1000 (EST) Date: Wed, 5 Jul 2006 11:36:24 +1000 From: Nathan Scott To: Nickolay Cc: Mike Montour , xfs@oss.sgi.com, mike.miller@hp.com, iss_storagedev@hp.com Subject: Missing cciss ioctl handler? (was Re: BUG with inode allocating) Message-ID: <20060705113624.A1521039@wobbly.melbourne.sgi.com> References: <44AA54BB.7040608@protei.ru> <44AAB05D.8010106@bycast.com> <44AAC10D.1040206@protei.ru> <44AAC864.3090507@bycast.com> <44AAD018.9090400@protei.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <44AAD018.9090400@protei.ru>; from nickolay@protei.ru on Wed, Jul 05, 2006 at 12:31:20AM +0400 X-archive-position: 8116 X-ecartis-version: Ecartis v1.0.0 Sender: xfs-bounce@oss.sgi.com Errors-to: xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: xfs Content-Length: 608 Lines: 22 On Wed, Jul 05, 2006 at 12:31:20AM +0400, Nickolay wrote: > ... > New version works fine, but with a warning(can't get sector size), > new mkfs.xfs warns too. > > This is a new result: > > -------------------------------------------- > root@192_168_15_15:/usr/test$ xfs_db -r -c "freesp -s" /dev/cciss/c0d0p2 > xfs_db: warning - cannot get sector size from block device > /dev/cciss/c0d0p2: Invalid request code > ... This is a problem in the cciss kernel driver, its not handling the BLKSSZGET ioctl (adding people from the kernel MAINTAINERS file to the CC to get that fixed up). cheers. -- Nathan