Bug #571
closedPanic on reboot: dangling vnode
0%
Description
http://www.punchyouremployer.com/images/PIC_0209.JPG
Not sure if its 100% reproducable but what I did was i mounted a fat32
filesystem over ntfs and then rebooted.
Petr
Updated by dillon almost 18 years ago
:http://www.punchyouremployer.com/images/PIC_0209.JPG
:
:Not sure if its 100% reproducable but what I did was i mounted a fat32
:filesystem over ntfs and then rebooted.
:
:Petr
It is probably easily reproducable. Now I just need an NTFS image to
test it with :-)
The umount code is probably forgetting to dereference the mount point
in either ntfs or msdosfs, and this likely causing the panic.
-Matt
Matthew Dillon
<dillon@backplane.com>
Updated by dillon almost 18 years ago
:
:http://www.punchyouremployer.com/images/PIC_0209.JPG
:
:Not sure if its 100% reproducable but what I did was i mounted a fat32
:filesystem over ntfs and then rebooted.
:
:Petr
Oh, another question in addition to my last question... were you
CD'd into either the ntfs or the dos filesystem when you rebooted?
Does the problem still occur if you are CD'd into / when rebooting?
-Matt
Matthew Dillon
<dillon@backplane.com>
Updated by dillon almost 18 years ago
:http://www.punchyouremployer.com/images/PIC_0209.JPG
:
:Not sure if its 100% reproducable but what I did was i mounted a fat32
:filesystem over ntfs and then rebooted.
:
:Petr
Heh. If people keep on posting JPGs I'll start asking for you all to
install ImageMagic and use the 'convert' utility to reduce the quality
of the JPGs to make them smaller :-)
If you unmount the fat32 filesystem before rebooting, it doesn't
generate the panic, right?
-Matt
Matthew Dillon
<dillon@backplane.com>
Updated by elekktretterr almost 18 years ago
Unfortunately, I was unable to reproduce it at all :(
I think that just before I rebooted i tried to copy a dvd image to the
fat32 file system, and after copying 4gb it say the file is too large,
so i deleted it, but thats about it.
Btw, can the 4gb limit be removed?
The sole reason why i had to move a dvd image was because i have been
unable to burn dvds in DragonFly for a long time. I used to use
growisofs in linux but for some reason the program write a couple of
bytes and then exits, practically fucking up the dvd. dvdrecord has the
same problem as cdrecord, it cant find the SCSI subsystem
elevator# cdrecord scanbus) Copyright (C) 1995-2002 Jörg Schilling
Cdrecord 2.00.3 (-
cdrecord: No local SCSI transport implementation for this architecture.
I'd be happier if i could start buring dvds than having to move them to
fat32 and burn from windows.
Thanks a lot,
Petr
Updated by ezra almost 18 years ago
Petr i was looking at your post in Bugs, about your inability to burn
dvd on dragonfly. I think you are using the wrong cdrecord version, the
one that comes with iso. My suggestion is to uninstall it and install
cdrtools-ossdvd from pkgsrc.
Updated by justin almost 18 years ago
dvd+rw-tools is what I use, which has a dependency on cdrtools-ossdvd.
growisofs, from dvd+rw-tools, seems to burn DVDs just fine.
Updated by elekktretterr almost 18 years ago
Thanks Ezra and Justin. I installed sysutils/cdrtools-ossdvd after
uninstalling sysutils/cdrtools and now it detects my dvd recorder :) Im
installing growisofs now to test it again and will post an update.
It would still be nice if the 4gb size limit was removed though,
especially now when dvd's are pretty much standard for everything except
audio.
Petr
Updated by corecode almost 18 years ago
i tried growisofs some days ago, worked.
you have atapicam?
cheers
simon
Updated by TGEN almost 18 years ago
Doesn't ISO9660 limit maximum filesizes to 4*2^30 bytes? Same goes for
FAT32 btw, afaik.
Cheers,
--
Thomas E. Spanjaard
tgen@netphreax.net
Updated by elekktretterr over 17 years ago
The problem wasnt solved because none of us can reproduce it.