Date: Sat, 1 Jun 2019 13:31:18 -0300 From: "Nenhum_de_Nos" <matheus@eternamente.info> To: freebsd-stable@freebsd.org Subject: Re: Gmirror and bigger disks (growfs) Message-ID: <e83c1870b2a02f85bf08e1fdd0df0757.squirrel@10.1.1.11> In-Reply-To: <d30b065f-06a5-0d33-5af8-2eec541d6cc8@grosbein.net> References: <01f6a0b0e75ea4f49601b155d54bad0d.squirrel@10.1.1.11> <d30b065f-06a5-0d33-5af8-2eec541d6cc8@grosbein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, June 1, 2019 09:57, Eugene Grosbein wrote: > 01.06.2019 19:04, Nenhum_de_Nos wrotr: >> Hi, >> >> I replaced a faulty disk from a gmirror some time ago. The array had two >> 1TB disks and I got one 2TB disk there. Now I replaced the second one >> and >> tried to growfs it. No good for me. > > First you need to resize the mirror itself with "gmirror resize" command. > Refer to gmirror(8) manual page for details. > > Then you need to resize last slice or create new slice for available > space. > If you prefer resize existing slice, use "gpart resize". > > Only then you will be able to run growfs to utilise new space for file > system inside the slice. Hi Eugene, thanks! I will try this in a couple of hours. I created the slices already at max size, even so I need to use all those commands? thanks, I was searching on the wrong place, way too wrong... thanks, matheus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e83c1870b2a02f85bf08e1fdd0df0757.squirrel>