Date: Mon, 7 Nov 2005 00:19:25 +0100 From: Oliver Brandmueller <ob@e-Gitt.NET> To: freebsd-current@freebsd.org Subject: Re: May be a bug in fsck [ after super block crash on 5.4-STABLE ] Message-ID: <20051106231925.GC23749@e-Gitt.NET> In-Reply-To: <20051106211124.GL91530@cell.sick.ru> References: <84099c3d0511030325q6d1df92ag77310ff1b03a2d15@mail.gmail.com> <84099c3d0511030425q3592a288he254cb5f97f976b6@mail.gmail.com> <20051106144917.GA81664@comp.chem.msu.su> <a78074950511060705r500e0789y786af5d937bf1680@mail.gmail.com> <20051106211124.GL91530@cell.sick.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi. On Mon, Nov 07, 2005 at 12:11:24AM +0300, Gleb Smirnoff wrote: > X> That's correct. Fortunately, given that we have some ways to validate > X> whether the superblock is valid, it is not too hard to automatically > X> detect which type the FS actually is. > > I think this feature is already present in libufs, since dumpfs(8) > can detect UFS1/UFS2 type of filesystem. Well, the original problem was in incorrect superblock. To find the second one you need to check 32 or 160 for an valid superblock. If you can get the information if it's UFS1 or UFS2 only from the superblock, then you gotta check both (in the worst case). Kinda chicken and egg problem. - Oliver -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051106231925.GC23749>