Hi, all, I have a system with 12 S-ATA disks attached that I set up as a raidz2: %zpool status zfs pool: zfs state: ONLINE scrub: scrub in progress for 0h5m, 7.56% done, 1h3m to go config: NAME STATE READ WRITE CKSUM zfs ONLINE 0 0 0 raidz2 ONLINE 0 0 0 da0 ONLINE 0 0 0 da1 ONLINE 0 0 0 da2 ONLINE 0 0 0 da3 ONLINE 0 0 0 da4 ONLINE 0 0 0 da5 ONLINE 0 0 0 da6 ONLINE 0 0 0 da7 ONLINE 0 0 0 da8 ONLINE 0 0 0 da9 ONLINE 0 0 0 da10 ONLINE 0 0 0 da11 ONLINE 0 0 0 errors: No known data errors We are currently tweaking kernel memory a bit but the on disk data and the hardware seem to be just fine. 7-STABLE, amd64, 4 GB of RAM. A couple of days ago, at each boot we saw this error message: GEOM: da0: corrupt or invalid GPT detected. GEOM: da0: GPT rejected -- may not be recoverable. There should not be any partition, MBR or GPT on the disks, I created the zpool on the raw devices. So I figure: Somehow zfs wrote some data to da0 that somewhat resembles a GPT partition table, so GEOM gets confused at boot time. Question is: can somebody confirm my guess? If yes should I just ignore the message, can it be disabled somehow (compile kernel without GPT?) or should zpools be created on slices instead of disks? Thanks for any hints, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 info@punkt.de http://www.punkt.de Gf: J?rgen Egeling AG Mannheim 108285
On Mon, Jun 29, 2009 at 12:43 PM, Patrick M. Hausen<hausen@punkt.de> wrote:> Hi, all, > > I have a system with 12 S-ATA disks attached that I set up > as a raidz2: > > %zpool status zfs > ?pool: zfs > ?state: ONLINE > ?scrub: scrub in progress for 0h5m, 7.56% done, 1h3m to go > config: > > ? ? ? ?NAME ? ? ? ?STATE ? ? READ WRITE CKSUM > ? ? ? ?zfs ? ? ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ?raidz2 ? ?ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da0 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da1 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da2 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da3 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da4 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da5 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da6 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da7 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da8 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da9 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da10 ? ?ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da11 ? ?ONLINE ? ? ? 0 ? ? 0 ? ? 0 > > errors: No known data errorsI can't address your issue at hand, but I would point out that having a raidz/raidz2 consisting of more than 9 vdevs is a BAD IDEA (tm). All SUN documentation recommends using groups from 3 to 9 vdevs in size. There are known cases where using more vdevs than recommended causes performance degradation and more importantly, parity computation problems which can result in crashes and potential data loss. In your case, I would have the pool built as a group of 2 x 6-disk raidz. Sincerely, - Dan Naumov
On Mon, Jun 29, 2009 at 11:43, Patrick M. Hausen<hausen@punkt.de> wrote:> Hi, all, > > I have a system with 12 S-ATA disks attached that I set up > as a raidz2: > > %zpool status zfs > ?pool: zfs > ?state: ONLINE > ?scrub: scrub in progress for 0h5m, 7.56% done, 1h3m to go > config: > > ? ? ? ?NAME ? ? ? ?STATE ? ? READ WRITE CKSUM > ? ? ? ?zfs ? ? ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ?raidz2 ? ?ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da0 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da1 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da2 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da3 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da4 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da5 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da6 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da7 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da8 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da9 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da10 ? ?ONLINE ? ? ? 0 ? ? 0 ? ? 0 > ? ? ? ? ? ?da11 ? ?ONLINE ? ? ? 0 ? ? 0 ? ? 0 > > errors: No known data errors > > We are currently tweaking kernel memory a bit but the on disk > data and the hardware seem to be just fine. > > 7-STABLE, amd64, 4 GB of RAM. > > A couple of days ago, at each boot we saw this error message: > > GEOM: da0: corrupt or invalid GPT detected. > GEOM: da0: GPT rejected -- may not be recoverable. > > > There should not be any partition, MBR or GPT on the disks, > I created the zpool on the raw devices. > > So I figure: > > Somehow zfs wrote some data to da0 that somewhat resembles a > GPT partition table, so GEOM gets confused at boot time. > > Question is: can somebody confirm my guess? If yes should I > just ignore the message, can it be disabled somehow (compile > kernel without GPT?) or should zpools be created on slices instead > of disks?Hi, could you post the output of dd if=/dev/da0 count=1 | hd
Hi, On Mon, Jun 29, 2009 at 01:11:16PM +0200, Marius N?nnerich wrote:> > GEOM: da0: corrupt or invalid GPT detected. > > GEOM: da0: GPT rejected -- may not be recoverable.> could you post the output of > dd if=/dev/da0 count=1 | hd512 bytes transferred in 0.038030 secs (13463 bytes/sec) 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000001b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff |................| 000001c0 ff ff ee ff ff ff 01 00 00 00 ff ff ff ff 00 00 |................| 000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| 00000200 Kind regards, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 info@punkt.de http://www.punkt.de Gf: J?rgen Egeling AG Mannheim 108285