Is there anything that can be done to 'fix' this? Under 4.x, using unionfs (and don't respond if your only answer is "its broken"), if it crashes, fsck finds a whack of the above ... Now, I think I understand the *why* for the error ... union creates a 'mirror' of the file system, especially where a du/find is concerned, and teh ZLDs are 'end nodes' that have no files under them ... but is there a better way that fsck can handle those? Its almost as if it doesn't know what to do with them, so has to remove them all ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
Hello!
I have some strange errors with burning a DVD.
In the beginning of the burn-process, burncd stopps
and writes the following output to /var/log/messages.
Jul 27 23:21:36 master kernel: acd0: FAILURE - START_STOP timed out
Jul 27 23:22:06 master kernel: acd0: TIMEOUT - READ_BIG retrying (2 retries
left)
Jul 27 23:22:36 master kernel: acd0: WARNING - READ_BIG interrupt was seen
but timeout fired
Jul 27 23:23:06 master kernel: acd0: WARNING - READ_BIG interrupt was seen
but taskqueue stalled
After the aborted burn-process, neither the system is accessible
via ssh nor any other process do their normal job. (Even though
some processes "seems" to work, e.g. ssh asks me about login/password
but doesn't give me access to the machine.) Furthermore, it is not
possible to manually eject the DVD by pressing the eject button
or by using the "cdrontrol eject" command. Unfortenuately, a reboot
helps.
Due to the fact that the obove mentioned error occurs exactly
once a week with the same DVD-media, I suppose that this
media is the originator of the problem. But anyhow, shouldn't
the system be in a stable mode, even if I use a bad media?
And maybe someone can give me a hint what
the kernel message means?
Thanks for clearing that up!
Christian
uname -rps : FreeBSD 5.2.1-RELEASE-p6 i386
burncd command: /usr/sbin/burncd -q -f /dev/acd0 -s max dvdrw image.iso
2>&1 | tee -a ${LOGFILE}
atacontrol info 1
Master: acd0 <PLEXTOR DVDR PX-504A/1.01> ATA/ATAPI rev 0
Slave: no device present
dmesg | grep -A1 -B1 -i acd0
IP Filter: v3.4.31 initialized. Default = block all, Logging = enabled
acd0: CDRW <PLEXTOR DVDR PX-504A> at ata1-master PIO4
em0: Link is up 1000 Mbps Full Duplex
On Tue, 27 Jul 2004, Marc G. Fournier wrote:> Is there anything that can be done to 'fix' this? Under 4.x, using > unionfs (and don't respond if your only answer is "its broken"), if it > crashes, fsck finds a whack of the above ...It's broken. :-) But in all honesty, this has been discussed extensively, and it's carefully documented in the man page. So if you run into bugs, it should not be a surprise.> Now, I think I understand the *why* for the error ... union creates a > 'mirror' of the file system, especially where a du/find is concerned, > and teh ZLDs are 'end nodes' that have no files under them ... but is > there a better way that fsck can handle those? Its almost as if it > doesn't know what to do with them, so has to remove them all ...Are you using union mounting of UFS or unionfs? Theory tells us that unionfs is a stacked file system layer, and shouldn't directly manipulate the on-disk layout of UFS, instead, issuing vnode operations that allow UFS to maintain its consistency guarantees. Theory tells us that union mounting UFS relies on UFS doing the magic, which means it has more opportunity to currupt on disk storage. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research