Hi Kyle,
given that what happens looks ever-so-slightly different each time, a
hardware glitch could be possible; to exclude this, would you happen to
know whether these panics occurred before build 78 as well ? If they occur
if you use the b77 hsfs module on your post-b78 system ? Does the
[EMAIL PROTECTED] wrote:
There have been two changes to HSFS in b78 as far as I remember (the
readahead speed improvements and the hardlink support), I wouldn't
associate either with e.g. screwed vfs linkage (as two of these
stacktraces show), but then, stranger regressions have occurred.
I have sNV b78 installed (I know I'm working on upgrading to b90.)
Is that an official snv_78 build, or did you compile that from onnv-gate
mercurial sources (post snv_77)?
I was attempting to mount /dev/dsk/c2t0d0s4, which is an ATAPI DVDROM
drive containing S10 03/05 CD1, and the machine
Hi All,
I have sNV b78 installed (I know I'm working on upgrading to b90.)
I was attempting to mount /dev/dsk/c2t0d0s4, which is an ATAPI DVDROM
drive containing S10 03/05 CD1, and the machine panic'd when I did
'mount -F hsfs -o ro /dev/dsk/c2t0d0s4'
Here's what came up on the console... I
It happenned again. Only this time it happenned when I started 'bash'
(after failing[no such device] to mount s7 of the same CD.)
Here's the panic this time:
# mount -F hsfs -o ro /dev/dsk/c2t0d0s7 /mnt
mount: /dev/dsk/c2t0d0s7 no such device
# bash
panic[cpu0]/thread=ff02d58d46e0: BAD
And Again.
I don't know enough about the panic dumps to say if they're the same or
not, but I've been doing (slightly) different things st the time of each
panic.
Here's the latest dump:
# mount -o ro /dev/dsk/c2t0d0s1 /mnt1
Jun 11 17:02:26 Boot ufs: NOTICE: mount: not a UFS magic number
