Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 16 Oct 2007 17:13:56 +0300
From:      Andriy Gapon <avg@icyb.net.ua>
To:        d_elbracht <d_elbracht@ecngs.de>
Cc:        freebsd-geom@freebsd.org, freebsd-stable@freebsd.org, 'Ivan Voras' <ivoras@freebsd.org>
Subject:   Re: AW:  Re: AW: g_vfs_done():da3s1a[READ(offset=81064794762854400,  length=8192)]error = 5
Message-ID:  <4714C724.6000809@icyb.net.ua>
In-Reply-To: <1192540986.00814865.1192529403@10.7.7.3>
References:  <1192382586.00813930.1192369201@10.7.7.3> <1192414981.00814129.1192401601@10.7.7.3> <1192447399.00814254.1192437006@10.7.7.3> <1192468999.00814418.1192458001@10.7.7.3> <1192540986.00814865.1192529403@10.7.7.3>

next in thread | previous in thread | raw e-mail | index | archive | help

Just a wild shot here: I have seen a similar message recently when I
played with my disks. I re-arranged some partitions (and filesystems)
within a slice and it so happened (and I almost know why) that there was
some discrepancy between on-disk and in-memory label of that slice. I
ran newfs on one of the new partitions and apparently it used one label
to determine its size, but after the reboot the other label was used. As
a result I had a UFS2 filesystem with size larger than a partition that
hosted it. And after that I saw the messages similar to the one in the
subject.

All of the above is a result of my understanding of how these things
work, so it may be incorrect. But making sure that disklabels match
(that is, there is only one disklabel) and re-newfs-ing the filesystems
did help me.

So I would compare, just in case, outputs of, say, 'dumpfs -m' near '-s'
and disklabel output.

Just my 2 bits.


P.S. example of the error that I had:
g_vfs_done():ad4s1e[READ(offset=20420280320, length=16384)]error = 5

-- 
Andriy Gapon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4714C724.6000809>