Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 13 Aug 2002 18:36:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 13 Aug 2002 18:36:36 -0400 Received: from tone.orchestra.cse.unsw.EDU.AU ([129.94.242.28]:50331 "HELO tone.orchestra.cse.unsw.EDU.AU") by vger.kernel.org with SMTP id ; Tue, 13 Aug 2002 18:36:35 -0400 From: Neil Brown To: Helge Hafting Date: Wed, 14 Aug 2002 08:40:17 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15705.35537.28818.387927@notabene.cse.unsw.edu.au> Cc: linux-kernel@vger.kernel.org Subject: Re: Various trouble in 2.5.31 In-Reply-To: message from Helge Hafting on Tuesday August 13 References: <3D58F932.4D87A904@aitel.hist.no> X-Mailer: VM 7.03 under Emacs 21.2.1 X-face: [Gw_3E*Gng}4rRrKRYotwlE?.2|**#s9D Some problems and oddities I have seen: > > * raid has trouble, even with 4k maximum bio's. > The bootup e2fsck complains that it can't find a valid > superblock on my raid-1 and raid-0 devices, although > mount has no trouble. I get logged complaints about > e2fsck using outdated ioctl's for md. Strange that > fsck should needs to know about raid devices. > Possibly a problem with e2fsck 1.27? The warning about ioctl's is fairly bogus. It gets reported for *any* unknown ioctl, whether it looks like it might be raid related or not. So I wouldn't worry about that. I have a new collection of patches for md which break if fairly thoroughly. I am about to started testing/fixing and will make sure that mkfs/fsck/mount work for raid{linear,0,1,5}. Thanks, NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/