Date: Mon, 06 Dec 2004 11:44:44 -0800 From: Manfred Antar <null@pozo.com> To: freebsd-current@freebsd.org Subject: Re: dump broken with new kernel Message-ID: <6.2.0.14.2.20041206114020.08851e60@pozo.com> In-Reply-To: <20041206171748.GB32801@dragon.nuxi.com> References: <6.2.0.14.2.20041206075313.03e74db8@pozo.com> <20041206171748.GB32801@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 09:17 AM 12/6/2004, you wrote: >On Mon, Dec 06, 2004 at 08:01:01AM -0800, Manfred Antar wrote: >> When I try to do a dump of the root filesystem I get : >> >> mksnap_ffs: Cannot create //.snap/dump_snapshot: Invalid argument >> dump: Cannot create //.snap/dump_snapshot: No such file or directory >> >> A kernel from a week ago works fine. >> The command I'm using is: >> dump 0Lfua /dev/nsa0 /dev/ad0s1a >> >> The .snap directory does exist and it is: >> drwxrwx--- 2 root operator 512 Dec 6 07:52 .snap > >I got this over the week end as I was trying to move some file systems to >a new disk. By chance can you use a binary search and track it down to a >particular day or maybe even the exact commit? > >-- >-- David (obrien@FreeBSD.org) It happened sometime between the 3rd and 4th. cvs co -D3-dec sys Works cvs co -D4-dec sys Is broken I'm also seeing alot of : Dec 6 10:06:53 pozo kernel: Accounting resumed Dec 6 10:07:23 pozo kernel: Accounting suspended Dec 6 10:07:38 pozo kernel: Accounting resumed Dec 6 10:12:23 pozo kernel: Accounting suspended Dec 6 10:12:38 pozo kernel: Accounting resumed Dec 6 10:12:53 pozo kernel: Accounting suspended This is with a new kernel and I don't think it is same as the dump problem as the kernel from the 4th doesn't do that. I'll try and narrow down the time a bit closer ================================== || null@pozo.com || || Ph. (415) 681-6235 || ==================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.2.0.14.2.20041206114020.08851e60>