На Wednesday 19 December 2007 10:37:46 Nikos Ntarmos написа:
Do you have any pointers to that thread? I did a quick search in
hackers@ and current@ but failed to find anything relevant, other than
people reporting related crashes and don't do that, then-type answers.
I started a thread a while
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Dec 18, 2007 at 10:03:42PM +1030, Daniel O'Connor wrote:
On Tue, 18 Dec 2007, Nikos Ntarmos wrote:
Off the top of my head, what is wrong/hard with just logging a device
failure, discarding all remaining cached operations, and unmounting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Dec 18, 2007 at 01:13:55AM +0100, Romain Tartière wrote:
On Mon, Dec 17, 2007 at 10:32:48AM -0800, Yuri wrote :
In case of USB device (which device in question in this problem
happens to be) usbd can be used to mount it.
If
On Tue, 18 Dec 2007, Nikos Ntarmos wrote:
Off the top of my head, what is wrong/hard with just logging a device
failure, discarding all remaining cached operations, and unmounting
the fs when a disk device goes missing? I understand that this is not
a viable solution for critical filesystems,
The problem is that the detach event can be caught only too late to
unmount the device properly. How may it be possible to sync a disk
``as soon as it is detached'' (that is when it is not physically
connected to the computer anymore)? Mounting the disk read-only may
be a workaround,
On Tue, 18 Dec 2007, [EMAIL PROTECTED] wrote:
Unfortunately, they do happen fairly often, usually caused by
USB-related stuff (FreeBSD's USB stack is _the_ worst I've seen lately
-- I take it that the stack's favorite hobby is panicking the kernel
with unrivaled efficiency), sometimes by
Yuri wrote:
I had USB camera connected and recognized as umass0 and mounted as /mnt/camera
on /dev/da0s1.
Camera was disconnected while it was still mounted.
I've understood that the only solution to this currently is don't do
that then. :)
___
Hi
On Mon, Dec 17, 2007 at 03:07:02AM -0800, Yuri wrote :
I had USB camera connected and recognized as umass0 and mounted as /mnt/camera
on /dev/da0s1.
Camera was disconnected while it was still mounted.
Personal recipe when this kind of things happens (generally caused by a
camera
On Mon, Dec 17, 2007 at 08:58:27AM -0600, Sergey Babkin wrote :
Would not umount -f do the trick?
I tried it without particular care one time on a failing device and
experienced an instant system reboot (was it caused by the faulty disk
or by a limitation in the implementation of the system
On Mon, Dec 17, 2007 at 03:07:02AM -0800, Yuri wrote :
I had USB camera connected and recognized as umass0 and mounted as
/mnt/camera
on /dev/da0s1.
Camera was disconnected while it was still mounted.
Personal recipe when this kind of things happens (generally caused by a
camera switching
On Mon, Dec 17, 2007 at 03:07:02AM -0800, Yuri wrote:
I had USB camera connected and recognized as umass0 and mounted as /mnt/camera
on /dev/da0s1.
Camera was disconnected while it was still mounted.
This triggers known and extremely painful to fix bugs in FreeBSD.
Your best work-around is to
I had USB camera connected and recognized as umass0 and mounted as
/mnt/camera
on /dev/da0s1.
Camera was disconnected while it was still mounted.
I submitted this late at night. Now in the morning another solution
came to my mind. I thought I will find it in replies but I didn't.
In case
On 18/12/2007 5:09 AM, Peter Jeremy wrote:
On Mon, Dec 17, 2007 at 03:07:02AM -0800, Yuri wrote:
I had USB camera connected and recognized as umass0 and mounted as /mnt/camera
on /dev/da0s1.
Camera was disconnected while it was still mounted.
This triggers known and extremely painful to fix
On Mon, Dec 17, 2007 at 10:32:48AM -0800, Yuri wrote :
In case of USB device (which device in question in this problem
happens to be) usbd can be used to mount it.
If attach/detach events trigger mount/unmount commands this problem
shouldn't exist. I didn't try though.
The problem is that
Hi Antony,
On Tue, Dec 18, 2007 at 09:36:19AM +1100, Antony Mawer wrote :
Every time this comes up it's branded with the really hard to fix
message, but I seem to recall the last time this came up Matt Dillon
chimed in and said he'd managed to fix it in Dragonfly without too
much pain.
I
15 matches
Mail list logo
