Date: Sat, 12 Jan 2008 01:05:47 +0000 From: Baldur Gislason <baldur@foo.is> To: freebsd-fs@freebsd.org Subject: GBDE problems Message-ID: <20080112010546.GI37723@gremlin.foo.is>
next in thread | raw e-mail | index | archive | help
I don't know if I'm posting this to the right list but I'm having some pretty nasty problems with GBDE on 2 seperate machines with very different setups. One is a 7.0-RC1 that was just installed a couple days ago and the other is a 6.2-REL. Both exhibit the same problem, when doing any intensive I/O on the gbde device (copying files around, etc) they both flood the console with messages like this: g_vfs_done():ad11s1d.bde[READ(offset=-8478054264274608128, length=65536)]error = 5 g_vfs_done():ad11s1d.bde[READ(offset=4422716238718156800, length=65536)]error = 5 g_vfs_done():ad11s1d.bde[READ(offset=-8478054264274608128, length=65536)]error = 5 g_vfs_done():ad11s1d.bde[READ(offset=4422716238718156800, length=65536)]error = 5 g_vfs_done():ad11s1d.bde[READ(offset=-8478054264274608128, length=65536)]error = 5 This is from the 7.0-RC1 machine, which for performance reasons has the block size in gbde set to 8192 bytes and the fragment size in UFS2 set to the same and block size in UFS2 set to 8x that or 65536 as adviced in the newfs man page. The 6.2 machine has the storage sitting on an atapi raid device (ar0) and I'm using 2048 byte block size in GBDE and default settings for UFS2. I have soft updates turned on in both cases. Can anyone give me some advice on how to tackle this? Baldur Gislason baldur@foo.is
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080112010546.GI37723>