NetBSD-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Spontaneous reboots on 5.99.59/i386 on a Thinkpad X41
On Mar 9, 2012, at 9:42 AM, Ignatios Souvatzis wrote:
> Hi,
>
> On Fri, Mar 02, 2012 at 02:47:25PM +0100, Moritz Wilhelmy wrote:
>> On Fri, Mar 02, 2012 at 10:36:51 +0100, J. Hannken-Illjes wrote:
>>> Please be a bit more verbose, what fss experiments, what file systems?
>>
>> UFS2 on /, creating a snapshot while simultaneously using WAPBL.
>> Creation itself went fine, but when I rebooted, the kernel started
>> panicking. As mentioned, I got several crashdumps which I intended to
>> debug.
>> Then, suddenly and out of the blue, the system started rebooting when I
>> start urxvt. It doens't happen with other programs I tried, e.g. xterm
>> works. However, I decided not to use the machine for the moment.
>
> This reminds me that I don't think I ever reported...
>
> 5.99.something (nearly a year ago), wapbl, ffs on single-CPU sparc64.
>
> Got a panic doing rsync from the snapshot. No problems without ffs, so
> I reverted to the orinal script. It's a production server, so no time
> for experiments.
>
> What I exactly did:
>
> doone () {
> echo Working on $3...
> fssconfig -x fss0 $3 $3/.fssbackup || exit 1
> mount /dev/fss0 /mnt1 || exit 1
> fsck -p /dev/$1 || exit 1
> mount /dev/$2 /mnt2 || exit 2
> rsync -ax /mnt1/. /mnt2/.
> umount /mnt2
> umount /mnt1
> fssconfig -u fss0
> }
> doone rsd0a sd0a /.
> doone rsd0d sd0d /var
> doone rsd0g sd0g /usr
Just tried it here:
NetBSD 6.99.3, i386, 4 cpu, wapbl enabled root
$ dumpfs / | grep wapbl
wapbl version 0x1 location 2 flags 0x0
wapbl loc0 7835392 loc1 16096 loc2 512 loc3 8
flags wapbl
No panic, no crash, only:
/dev/fss0: file system not clean (fs_clean=0x4); please fsck(8)
/dev/fss0: lost blocks 0 files 0
Should have mounted the snapshot read-only.
--
Juergen Hannken-Illjes - hannken%eis.cs.tu-bs.de@localhost - TU Braunschweig
(Germany)
Home |
Main Index |
Thread Index |
Old Index