So far, after eliminating flush option, I achieved a speed of 3.9 MB/s
which was previously 1-2 MB/s.
If I could somehow force the async option, I think speed would
increase more. Any ideas ?
The async option appears true (configured) in hal-device, but doesn't
get mounted with that option.
--
On 03/14/10 12:30, Ray Rashif wrote:
Anyway, a slightly off-topic complaint I have is that my 32GB Cruzer
is slow as hell to write to at just a measly 3MB/s.
My SanDisk Sansa Clip in mass-storage mode is excessively slow (also,
Linux used to have difficulty mounting it in USB 2.0 mode and eith
f...@kokkinizita.net (2010-03-14 17:03):
> On Sun, Mar 14, 2010 at 08:58:45PM +0530, Nilesh Govindarajan wrote:
>
> > On 03/14/2010 08:50 PM, f...@kokkinizita.net wrote:
> >
> > >Just put the device in /etc/fstab with whatever options
> > >you want, (u)mount it manually and forget about hal.
> >
Hacked mount options by hal finally.
There is not much gain after disabling flush. I was getting 1-2 MB/s
before flush and now 3-4 MB/s
Approximately twice.
I used to get around 7-10 MB/s some time ago with my same pen drives.
I'm researching more to force async option.
I edited /usr/share/hal/
On 15 March 2010 00:03, wrote:
> On Sun, Mar 14, 2010 at 08:58:45PM +0530, Nilesh Govindarajan wrote:
>
>> On 03/14/2010 08:50 PM, f...@kokkinizita.net wrote:
>>
>> >Just put the device in /etc/fstab with whatever options
>> >you want, (u)mount it manually and forget about hal.
>>
>> Doesn't do g
Anyway, a slightly off-topic complaint I have is that my 32GB Cruzer
is slow as hell to write to at just a measly 3MB/s. Sheesh. I wonder
if it's the size and technical limitation or whether there might be
some untested hackery.
I was thinking of formatting it in Windows and changing the allocatio
Am oder ungefähr am Sonntag, 14. März 2010, schrieb f...@kokkinizita.net:
> On Sun, Mar 14, 2010 at 05:02:47PM +0100, Edgar Kalkowski wrote:
>
> > In this case you can either use labels or uuids to identify them in
> > /etc/fstab, e.g.
> >
> > /dev/disk/by-label/Data /mnt/Data vfat
> > uid=root
On Sun, Mar 14, 2010 at 05:02:47PM +0100, Edgar Kalkowski wrote:
> In this case you can either use labels or uuids to identify them in
> /etc/fstab, e.g.
>
> /dev/disk/by-label/Data /mnt/Data vfat
> uid=root,gid=users,showexec,user,noauto,umask=002,utf8,shortname=mixed 0 0
> /dev/disk/by-uuid/5
On Sun, Mar 14, 2010 at 08:58:45PM +0530, Nilesh Govindarajan wrote:
> On 03/14/2010 08:50 PM, f...@kokkinizita.net wrote:
>
> >Just put the device in /etc/fstab with whatever options
> >you want, (u)mount it manually and forget about hal.
>
> Doesn't do good. I have multiple pen drives :)
Same
Am oder ungefähr am Sonntag, 14. März 2010, schrieb Nilesh Govindarajan:
> On 03/14/2010 08:50 PM, f...@kokkinizita.net wrote:
> > On Sun, Mar 14, 2010 at 07:51:28PM +0530, Nilesh Govindarajan wrote:
> >
> > Just put the device in /etc/fstab with whatever options
> > you want, (u)mount it manually
On 03/14/2010 08:50 PM, f...@kokkinizita.net wrote:
On Sun, Mar 14, 2010 at 07:51:28PM +0530, Nilesh Govindarajan wrote:
@Ray,
If the device has small buffer size, then it takes lot of time. Who
want's to shell out more bucks for this simple flush thing to get a
device with bigger buffer size.
On Sun, Mar 14, 2010 at 07:51:28PM +0530, Nilesh Govindarajan wrote:
> @Ray,
> If the device has small buffer size, then it takes lot of time. Who
> want's to shell out more bucks for this simple flush thing to get a
> device with bigger buffer size.
>
> @Robert,
> Power would fail if there was n
On 03/14/2010 02:21 PM, Nilesh Govindarajan wrote:
> On 03/14/2010 07:41 PM, Robert Howard wrote:
>> Yes, it's all placebo effect. What seems like faster transfers is
>> really the
>> use of write caching and not a good idea for removable media. Could leave
>> the data and filesystem in inconsisten
On 03/14/2010 07:41 PM, Robert Howard wrote:
Yes, it's all placebo effect. What seems like faster transfers is really the
use of write caching and not a good idea for removable media. Could leave
the data and filesystem in inconsistent states if the device were
accidentally removed or if power fa
Yes, it's all placebo effect. What seems like faster transfers is really the
use of write caching and not a good idea for removable media. Could leave
the data and filesystem in inconsistent states if the device were
accidentally removed or if power failed.
On Mar 14, 2010 4:33 AM, "Ray Rashif" w
On 13/03/2010, Nilesh Govindarajan wrote:
> By default HAL adds the flush flag when USB devices are mounted... I
> think which is what making WRITEs slow.
> I want that HAL shouldn't add the flush flag. How to ?
Funny..I remember the very reason for making "flush" a default mount
option was becau
By default HAL adds the flush flag when USB devices are mounted... I
think which is what making WRITEs slow.
I want that HAL shouldn't add the flush flag. How to ?
--
Nilesh Govindarajan
Site & Server Administrator
www.itech7.com
17 matches
Mail list logo
