Date: Mon, 16 Feb 2004 12:09:35 +0100 From: Stijn Hoop <stijn@win.tue.nl> To: Lukas Ertl <l.ertl@univie.ac.at> Cc: freebsd-current@FreeBSD.org Subject: Re: Can't save Vinum config: No such file or directory Message-ID: <20040216110935.GA753@pcwin002.win.tue.nl> In-Reply-To: <20040213235341.L618@korben.in.tern> References: <20040213130520.GB714@pcwin002.win.tue.nl> <20040213175748.B662@korben.in.tern> <20040213173456.GH714@pcwin002.win.tue.nl> <20040213201416.E662@korben.in.tern> <20040213205311.GI714@pcwin002.win.tue.nl> <20040213235341.L618@korben.in.tern>
next in thread | previous in thread | raw e-mail | index | archive | help
--C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 13, 2004 at 11:55:41PM +0100, Lukas Ertl wrote: > I have a very very far fetched idea. Could you please try this: >=20 > *) cd /usr/src/sbin/vinum > *) vi commands.c > *) locate the function vinum_read(), the first line says "int error;" > *) initialize this var to zero, i.e. "int error =3D 0;" > *) recompile vinum and tell if that changed anything OK, more info now that I am at the console of the machine again. During the weekend I discovered that I had saved a copy of my previously working kernel somewhere in my homedirectory, so this morning I first compi= led a Feb 6 version of /sbin/vinum, and then booted off the old kernel + vinum module, and executed the old /sbin/vinum. No error message, but the only things listed in my configuration were the drives (so no volumes/plexes/subdisks). Next up I tried your suggestion above with my new kernel. This also got rid= of the error message (or at least it doesn't show up), but again the only obje= cts listed were the drives; no volumes etc. My current theory is that I somehow goofed up during the kernel rebuild-a-t= hon last friday, and that I somewhere loaded the old vinum module alongside the new kernel; and this bit me by overwriting my configuration. It's the only explanation I can think of (since I'm obviously the only one to have this problem). If you want more information or have more things I could try I'd be glad to do so, but I think that it was me that introduced this, alto= ugh I couldn't for the life of me think of anything I did that could cause this. Although the data that was on the volume is not crucial, it would be nice if there was a way to recover it; so if you don't want to investigate further, can you tell me whether a vinum create would restore my volumes, or is there simply no way that I can do so without obliterating the data? If the latter, I'll just move on and recreate the plex using ccd(4) (seeing as following vinum development is not one of my goals right now). --Stijn --=20 Apparently, 1 in 5 people in the world are Chinese. And there are 5 people in my family, so it must be one of them. It's either my mum or my dad...... or maybe my older brother John. Or my younger brother Ho-Cha-Chu. But I'm pretty sure it's John. --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAMKTvY3r/tLQmfWcRAu61AJ0SG+JTPK2cnYITyvxt5pZpMhLfEQCfd7eb 9XOedHDgGuqX9i/RhSqkTWg= =Y56n -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040216110935.GA753>