linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Iragne <florian.iragne@labri.fr>
To: linux-hotplug@vger.kernel.org
Subject: Re: add/remove actions for usb devices
Date: Tue, 30 Mar 2004 07:25:46 +0000	[thread overview]
Message-ID: <406920FA.50508@labri.fr> (raw)
In-Reply-To: <40648838.2040703@labri.fr>

jjluza wrote:
>>Florian Iragne wrote :
>>on device add, it is correctly mounted. on device removal, the system 
>>freeze and i have to use magic keys to reboot the machine.
>>
> 
> yes, that's the error I get.
> I'm pretty sure that's because vfat doesn't support sync mode.

No, i don't think so. I have a script that mount/umount devices 
automatically (wthout using udev event), and it works (with sync mode 
for vfat).

> If I don't make udev handle device removal, I can unmount it manually, but it 
> freeze too.

manually, sometimes it hangs, but not always, and without any error message

>>well, where do you see any mention of the limitation of the sync mode to 
>>ext*/ufs? i've read the manpage of mount several times, but did not find 
>>anything like the info you mentioned.
> 
> I have read it on the manual page from debian sid. I have read such a thing on 
> several web sites too, after searching on google, but some other sites tell 
> we can ... so I'm a bit disappointed.
> 
> you can read that from this manpage too :
> http://www.netadmintools.com/html/8mount.man.html
> 
>>the sync option today has effect only for ext2, ext3 and ufs)
> 
i will read those, but the manpage on my debian sid doesn't seem to be 
the same than yours. ;-)
> 
> 
> It would be so good if vfat be aware of sync and if my kernel doesn't oops on 
> device removal.

yes, it would be good

Florian



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2004-03-30  7:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-26 19:44 add/remove actions for usb devices Florian Iragne
2004-03-26 19:51 ` Greg KH
2004-03-26 21:13 ` Florian Iragne
2004-03-26 21:22 ` Florian Iragne
2004-03-26 22:59 ` Greg KH
2004-03-28 12:05 ` Florian Iragne
2004-03-28 13:45 ` Florian Iragne
2004-03-28 13:52 ` Kay Sievers
2004-03-28 14:08 ` Martin Lohmeier
2004-03-28 14:35 ` jjluza
2004-03-28 14:58 ` Kay Sievers
2004-03-28 16:16 ` jjluza
2004-03-28 18:02 ` Florian Iragne
2004-03-28 18:19 ` Kay Sievers
2004-03-29 16:21 ` Florian Iragne
2004-03-29 16:36 ` Florian Iragne
2004-03-29 18:51 ` Patrick Mansfield
2004-03-29 19:11 ` Martin Lohmeier
2004-03-29 23:26 ` jjluza
2004-03-30  7:22 ` Florian Iragne
2004-03-30  7:25 ` Florian Iragne [this message]
2004-03-30  8:35 ` jjluza
2004-03-30  8:49 ` Florian Iragne
2004-03-30  9:48 ` jjluza

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=406920FA.50508@labri.fr \
    --to=florian.iragne@labri.fr \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).