From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1RTVB0-0005UC-Bc for garchives@archives.gentoo.org; Thu, 24 Nov 2011 09:01:02 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B276D21C041; Thu, 24 Nov 2011 09:00:53 +0000 (UTC) Received: from smtpq1.gn.mail.iss.as9143.net (smtpq1.gn.mail.iss.as9143.net [212.54.34.164]) by pigeon.gentoo.org (Postfix) with ESMTP id 55A6A21C028 for ; Thu, 24 Nov 2011 08:59:58 +0000 (UTC) Received: from [212.54.34.148] (helo=smtp16.gn.mail.iss.as9143.net) by smtpq1.gn.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1RTV9x-0002z1-Pl for gentoo-user@lists.gentoo.org; Thu, 24 Nov 2011 09:59:57 +0100 Received: from 5ed027a1.cm-7-1a.dynamic.ziggo.nl ([94.208.39.161] helo=data.antarean.org) by smtp16.gn.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1RTV9q-0001I3-0W for gentoo-user@lists.gentoo.org; Thu, 24 Nov 2011 09:59:57 +0100 Received: from localhost (localhost [127.0.0.1]) by data.antarean.org (Postfix) with ESMTP id EB7222976 for ; Thu, 24 Nov 2011 10:00:43 +0100 (CET) X-Virus-Scanned: amavisd-new at antarean.org Received: from data.antarean.org ([127.0.0.1]) by localhost (data.antarean.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u6JaL4gcq53F for ; Thu, 24 Nov 2011 10:00:41 +0100 (CET) Received: from www.antarean.org (net.antarean.org [10.10.11.5]) by data.antarean.org (Postfix) with ESMTP id B58612955 for ; Thu, 24 Nov 2011 10:00:41 +0100 (CET) Received: from 62.132.204.73 (SquirrelMail authenticated user joost) by www.antarean.org with HTTP; Thu, 24 Nov 2011 10:00:41 +0100 Message-ID: <15c5cec2bec92b20de89bf88dc15ebe9.squirrel@www.antarean.org> In-Reply-To: References: <20111117172550.2a04a59f@zaphod.digimed.co.uk> <20111117194754.6835abf6@digimed.co.uk> <20111117235934.30a2d6eb@digimed.co.uk> <20111118002143.09620c4b@zaphod.digimed.co.uk> Date: Thu, 24 Nov 2011 10:00:41 +0100 Subject: Re: [gentoo-user] Process to resize ext3 file system at the command line? From: "J. Roeleveld" To: gentoo-user@lists.gentoo.org User-Agent: SquirrelMail/1.4.21 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 (Normal) Importance: Normal Content-Transfer-Encoding: quoted-printable X-Ziggo-spambar: -- X-Ziggo-spamscore: -2.2 X-Archives-Salt: 20cd05f5-b349-4868-9354-5c44818b2d4c X-Archives-Hash: 6806bd75d3095d11c3c4c516702e021f On Fri, November 18, 2011 1:33 am, Mark Knecht wrote: > On Thu, Nov 17, 2011 at 4:21 PM, Neil Bothwick wro= te: >> On Thu, 17 Nov 2011 16:13:09 -0800, Mark Knecht wrote: >> >>> > Do you have separately partitioned drives with those partitions >>> > arranged into single-partition arrays, or do you have one RAID devi= ce >>> > that is then partitioned? >>> > >>> > If the latter, you should certainly work with the md device. >>> > >>> > I prefer to avoid all this confusion by creating a large, single >>> > partition array that I use an an LVM physical volume. >>> >>> Separately partitioned drives arranged into RAID arrays. >> >> So you have three partitions arranged into a single RAID5 partition, >> say /dev/md1? >> >> In that case, the size of /dev/md1 should already be correct and you >> only >> need to resize the filesystem and you should ignore my witterings abou= t >> fdisk that filed to take into account your use of RAID. >> resize2fs /dev/md1 should be all you need, you shouldn't even need to >> unmount the filesystem. >> > > I have 3 partitions which were previously RAID-1. I've already failed > one drive so at this moment it's a 2-drive RAID-1. I'm attempting to > get those two remaining 2 partitions converted to RAID-5 the command > suggested on the RAID list for doing that isn't working for me. > > Once the 250GB RAID-1 is converted to RAID-5 i have to add a new drive > back in to become a 3-drive RAID-5. The drive I add will be the drive > I just failed. > > c2stable ~ # mdadm --grow /dev/md6 --level=3D5 > mdadm: /dev/md6: could not set level to raid5 > c2stable ~ # > > c2stable ~ # mdadm -D /dev/md6 > /dev/md6: > Version : 1.1 > Creation Time : Thu Apr 15 10:45:35 2010 > Raid Level : raid1 > Array Size : 247416933 (235.96 GiB 253.35 GB) > Used Dev Size : 247416933 (235.96 GiB 253.35 GB) > Raid Devices : 2 > Total Devices : 2 > Persistence : Superblock is persistent > > Update Time : Thu Nov 17 13:27:20 2011 > State : clean > Active Devices : 2 > Working Devices : 2 > Failed Devices : 0 > Spare Devices : 0 > > Name : c2stable:6 (local to host c2stable) > UUID : 249c7331:a8203540:c8f3b020:fb30a66b > Events : 1039 > > Number Major Minor RaidDevice State > 0 8 6 0 active sync /dev/sda6 > 1 8 22 1 active sync /dev/sdb6 > c2stable ~ # I have never had to change a RAID-1 to RAID-5, but I would do it as follo= ws: 1) Fail 2 drives from the RAID-1 2) Remove those 2 drives from the RAID-1 3) Create a new RAID-5 (with failed disk) using the 2 removed drives 4) Copy the data over from the RAID-1 to the RAID-5 5) Remove the RAID-1 6) Add the third drive to the RAID-5 and let it rebuild. I don't know the commands for the above from memory, but I'm sure some of this is in the man-page. -- Joost > > >