Date: Thu, 18 May 2006 19:12:32 +0400 From: Yar Tikhiy <yar@comp.chem.msu.su> To: freebsd-current@freebsd.org Subject: Root FS corruption Message-ID: <20060518151232.GA37743@comp.chem.msu.su>
next in thread | raw e-mail | index | archive | help
Hi all, I saw the following / corruption in a fresh CURRENT when using nextboot. Of course, it wasn't the fault of nextboot itself, nextboot simply was the only utility to modify / in my case. I found the contents of nextboot.conf once in my custom /root/supfile, the other time in the stock /etc/protocols. /etc/protocols was large enough to see how the corruption had happened: the first fragment, 2048 bytes, of the file was replaced by the contents of nextboot.conf, zero padded. The / was a usual 2048/16384 UFS2 without soft-updates. The kernel was GENERIC. Forced fsck reported no problems at all. The / had never been dirty because I used nextboot to boot single-user with all FSen read-only and investigate a panic unrelated to FS. Did any one see a similar problem of fragment mis-allocation? -- Yar
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060518151232.GA37743>