On Mon, May 07, 2018 at 08:23:53PM -0500, Roger Heflin wrote:
> Generally when I am messing with usb drives I have used these 2 commands:
>
> grep Dirty /proc/meminfo (dirty is the amount of write buffers that
> need to be flushed for all disks, most will usually be the disk that
> was just copied
On 05/08/2018 10:18 AM, Bob Goodwin wrote:
> On 05/08/18 13:10, Rick Stevens wrote:
>> I've seen this issue reported to the Xfce group before and they still
>> haven't seemed to fix it. I have no idea why. Perhaps we should sharpen
>> our sticks a bit and poke them a bit more. It's been well over a
On 05/08/18 13:10, Rick Stevens wrote:
I've seen this issue reported to the Xfce group before and they still
haven't seemed to fix it. I have no idea why. Perhaps we should sharpen
our sticks a bit and poke them a bit more. It's been well over a year.
-
On 05/08/2018 10:04 AM, Bob Goodwin wrote:
> On 05/08/18 12:38, Rick Stevens wrote:
>> I have seen the same behavior under F27 and F28 using Xfce and USB
>> drives (the desktop freezes until the drive gets ejected--a manual
>> umount as root from the CLI completes immediately).
>
> "a manual umoun
On 05/08/18 12:38, Rick Stevens wrote:
I have seen the same behavior under F27 and F28 using Xfce and USB
drives (the desktop freezes until the drive gets ejected--a manual
umount as root from the CLI completes immediately).
"a manual umount as root from the CLI completes immediately)." Sure en
On 05/08/2018 09:38 AM, Rick Stevens wrote:
> On 05/07/2018 03:53 PM, Eyal Lebedinsky wrote:
>> On 08/05/18 07:48, Bob Goodwin wrote:
>>> .
>>>
>>> I've had this problem for more than a year but usually it only bothers
>>> mefor a moment and I move on. Today it was a bigger annoyance when I
>>> was
On 05/07/2018 03:53 PM, Eyal Lebedinsky wrote:
> On 08/05/18 07:48, Bob Goodwin wrote:
>> .
>>
>> I've had this problem for more than a year but usually it only bothers
>> mefor a moment and I move on. Today it was a bigger annoyance when I
>> was trying to diagnose a problem with a flash drive.
>>
On 05/07/18 21:23, Roger Heflin wrote:
Generally when I am messing with usb drives I have used these 2 commands:
grep Dirty /proc/meminfo (dirty is the amount of write buffers that
need to be flushed for all disks, most will usually be the disk that
was just copied to)
the second is "vmstat 1"
I don't sync like Bob does, I just watch the io to estimate the copy
time of whatever amount I am copying.
On Mon, May 7, 2018 at 8:34 PM, Cameron Simpson wrote:
> On 07May2018 20:23, Roger Heflin wrote:
>>
>> the second is "vmstat 1" and watch the bi/bo columns as they show
>> reads and writes
On 07May2018 20:23, Roger Heflin wrote:
the second is "vmstat 1" and watch the bi/bo columns as they show
reads and writes to the disk subsystem, if it umounts when the writes
stop that implies the sync may have returned before it actually did
all its work.
Do you actually see this happen? Jus
Generally when I am messing with usb drives I have used these 2 commands:
grep Dirty /proc/meminfo (dirty is the amount of write buffers that
need to be flushed for all disks, most will usually be the disk that
was just copied to)
the second is "vmstat 1" and watch the bi/bo columns as they show
On 05/07/18 19:35, Samuel Sieb wrote:
Then that supports my suggestion. Unless the the flash drive is
mounted with the "sync" option, the data is copied into the cache and
the copy command exits. The data is being written in the background,
but when you want to unmount the drive, it has to
On Mon, May 07, 2018 at 06:44:51PM -0400, Bob Goodwin wrote:
[ ... ]
> I copy the data to the device in a terminal, it takes perhaps 30 seconds,
> when finished I close that to make the flash drive free and then go to the
> desktop, click on the unmount and this last time waited ~125 seconds for
On 05/07/2018 03:44 PM, Bob Goodwin wrote:
On 05/07/18 18:04, Samuel Sieb wrote:
If it only happens after you write to it, maybe the drive is slow and
the cache flush is taking longer than you expect. Or is the first
paragraph meaning that you click unmount immediately after mounting it
and i
On Mon, 7 May 2018 18:44:51 -0400
Bob Goodwin wrote:
> I copy the data to the device in a terminal, it takes perhaps 30
> seconds, when finished I close that to make the flash drive free and
> then go to the desktop, click on the unmount and this last time waited
> ~125 seconds for it to unmoun
On 08/05/18 07:48, Bob Goodwin wrote:
.
I've had this problem for more than a year but usually it only bothers mefor a
moment and I move on. Today it was a bigger annoyance when I was trying to
diagnose a problem with a flash drive.
When I mount the device my clicking on mount on the desktop
On 05/07/18 18:04, Samuel Sieb wrote:
If it only happens after you write to it, maybe the drive is slow and
the cache flush is taking longer than you expect. Or is the first
paragraph meaning that you click unmount immediately after mounting it
and it still takes that long? Another possibilit
On 05/07/2018 02:48 PM, Bob Goodwin wrote:
When I mount the device my clicking on mount on the desktop icon that
pops up when it is plugged init then takes 2 minutes, I timed it today,
to release after clicking on unmount. I would like to reduce that to
something reasonable likeimmediately or n
.
I've had this problem for more than a year but usually it only bothers
mefor a moment and I move on. Today it was a bigger annoyance when I was
trying to diagnose a problem with a flash drive.
When I mount the device my clicking on mount on the desktop icon that
pops up when it is plugged
19 matches
Mail list logo
