Michael Lednev wrote:
Hello, Kris.
On 2 ?? 2008 ?., 14:07:36 you wrote:
KK> Yes, long-standing issue with unexpected mounted device removal. Don't
KK> do that :)
Thanks, already found this PR, it's already 5 yo, wow :)
There have been some recent partial workarounds committed in curren
Hello, Kris.
On 2 ?? 2008 ?., 14:07:36 you wrote:
KK> Yes, long-standing issue with unexpected mounted device removal. Don't
KK> do that :)
Thanks, already found this PR, it's already 5 yo, wow :)
--
Best regards,
Michael mailto:[EMAIL PROTECTED]
___
Michael Lednev wrote:
Hello, freebsd-questions.
After the following actions:
1. Insert USB Flash
2. mount_msdosfs /dev/da0s1 /mnt
3. Remove USB Flash
4. umount -f /mnt
I have kernel panic every time. Is this a known issue? My system is
FreeBSD 7.0-RC1 from 1.01.2008.
Yes, long-standing
Hello, freebsd-questions.
After the following actions:
1. Insert USB Flash
2. mount_msdosfs /dev/da0s1 /mnt
3. Remove USB Flash
4. umount -f /mnt
I have kernel panic every time. Is this a known issue? My system is
FreeBSD 7.0-RC1 from 1.01.2008.
--
Best regards,
Michael
eir
> photos. I attempted to "umount /mnt" and encountered an error,
> something along the lines of cannot contact device, (I don't remember
> exactly. No, I wasn't in the directory I was attempting to umount.).
> No other process was communicating with the device, ac
something along the lines of cannot contact device, (I don't remember
exactly. No, I wasn't in the directory I was attempting to umount.).
No other process was communicating with the device, according to the
camera it was 'idle'. I issued a "umount -f /mnt" command. Th
> > > 1. If I use "umount -f /dev/ad4s1a" to forcefully umount a
> > > file system, does this jeopardize the integrity of said
> > > file system? Like...will it jerk the run out from under
> > > a process in the middle of a disk write, thus leaving a
with a truncated (or
slightly mauled) file but never a corrupt filesystem.
Even kicking the power cord out only results in minor,
repairable corruption something like 30% of the time.
Again, in terms of personal experience I would suggest that
umount -f is shrug-inducingly "safe" at 3 o
drive (we'll say
> > /dev/ad4), without corrupting the file system and without bringing the
> > entire system down. I need to safely umount the file systems, even if my
> > users have processes which have files open.
> >
> > 1. If I use "umount -f /dev/ad4s1a
ging the
> entire system down. I need to safely umount the file systems, even if my
> users have processes which have files open.
>
> 1. If I use "umount -f /dev/ad4s1a" to forcefully umount a file system, does
> this jeopardize the integrity of said file system? Like...
even if my
users have processes which have files open.
1. If I use "umount -f /dev/ad4s1a" to forcefully umount a file system, does
this jeopardize the integrity of said file system? Like...will it jerk the
run out from under a process in the middle of a disk write, thus leaving a
half w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was transferring a huge file (700 MB) to an nfs mounted disc and I
umount -f the nfs mounted directory. After this I lost control of that pc
(I was remotely administering it). The machine responds to pings and
forwards packets as well, but if I try
12 matches
Mail list logo
