Re: Weird behavior writing to SSD on 2013 MacBook

2015-02-05 Thread Lundberg, Johannes
The only values that change are load and r. u and s are 0.00. If I wait long enough it always continues but might be several minutes. -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. On Thu, Feb 5, 2015 at 4:56 PM, Dimitry Andric d...@freebsd.org wrote: If you let bsdtar continue, and press

Re: Weird behavior writing to SSD on 2013 MacBook

2015-02-05 Thread Konstantin Belousov
On Thu, Feb 05, 2015 at 08:56:59AM +0100, Dimitry Andric wrote: If you let bsdtar continue, and press control-T a few times, does the user time (u) increase at all? Does it ever go any further, if you let it run for a very long time? I believe a problem may have been introduced by r277922,

Re: Weird behavior writing to SSD on 2013 MacBook

2015-02-05 Thread Alfred Perlstein
On 2/5/15 12:30 AM, Konstantin Belousov wrote: On Thu, Feb 05, 2015 at 08:56:59AM +0100, Dimitry Andric wrote: If you let bsdtar continue, and press control-T a few times, does the user time (u) increase at all? Does it ever go any further, if you let it run for a very long time? I believe

Re: Weird behavior writing to SSD on 2013 MacBook

2015-02-05 Thread Konstantin Belousov
On Thu, Feb 05, 2015 at 12:45:55AM -0800, Alfred Perlstein wrote: On 2/5/15 12:30 AM, Konstantin Belousov wrote: On Thu, Feb 05, 2015 at 08:56:59AM +0100, Dimitry Andric wrote: If you let bsdtar continue, and press control-T a few times, does the user time (u) increase at all? Does it

Re: Weird behavior writing to SSD on 2013 MacBook

2015-02-05 Thread Alfred Perlstein
It's possible original intent of that construct was just a pause/throttle if it used to be an if(). Makes sense although should investigate further. Sent from my iPhone On Feb 5, 2015, at 1:03 AM, Konstantin Belousov kostik...@gmail.com wrote: On Thu, Feb 05, 2015 at 12:45:55AM -0800,

Re: Weird behavior writing to SSD on 2013 MacBook

2015-02-05 Thread Lundberg, Johannes
It seems like the patch solved my problem. No more freezing of the filesystem. -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. On Thu, Feb 5, 2015 at 6:19 PM, Alfred Perlstein bri...@mu.org wrote: It's possible original intent of that construct was just a pause/throttle if it used to be an

Re: Weird behavior writing to SSD on 2013 MacBook

2015-02-05 Thread Dimitry Andric
On 05 Feb 2015, at 09:30, Konstantin Belousov kostik...@gmail.com wrote: On Thu, Feb 05, 2015 at 08:56:59AM +0100, Dimitry Andric wrote: If you let bsdtar continue, and press control-T a few times, does the user time (u) increase at all? Does it ever go any further, if you let it run for a

Weird behavior writing to SSD on 2013 MacBook

2015-02-04 Thread Lundberg, Johannes
Hi I'm thought I was gonna do some test runs with HEAD on a 2013 Macbook Air and noticed some weird behavior regarding disk I/O. This happens both when doing portsnap extract and clone from git repository. For example portsnap extract, the extraction process (the output of it) suddenly stops,

Re: Weird behavior writing to SSD on 2013 MacBook

2015-02-04 Thread Lundberg, Johannes
I deleted /usr/ports and did a new portsnap extract portsnap stopped at /usr/ports/editors/teco that folder is empty and the previous folder (editors/tea) is populated with files. portsnap stopped for about 2-3 minutes and during the whole time gstat showed values like this: (disc io load was

Re: Weird behavior writing to SSD on 2013 MacBook

2015-02-04 Thread Allan Jude
On 2015-02-04 19:29, Lundberg, Johannes wrote: Hi I'm thought I was gonna do some test runs with HEAD on a 2013 Macbook Air and noticed some weird behavior regarding disk I/O. This happens both when doing portsnap extract and clone from git repository. For example portsnap extract, the

Re: Weird behavior writing to SSD on 2013 MacBook

2015-02-04 Thread Lundberg, Johannes
By the way, For the second test I first ran portsnap extract without removing the old /usr/ports folder and it ran through quickly without any halts.. -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. On Thu, Feb 5, 2015 at 10:38 AM, Lundberg, Johannes johan...@brilliantservice.co.jp wrote: I

Re: Weird behavior writing to SSD on 2013 MacBook

2015-02-04 Thread Lundberg, Johannes
The release is the latest snapshot memstick image and kernel is from https://github.com/dumbbell/freebsd/tree/kms-drm-update-38. I think this problem existed before I changed kernel. I haven't changed any settings on the filesystem so I assume TRIM is off. When stopped bsdtar is in state

Re: Weird behavior writing to SSD on 2013 MacBook

2015-02-04 Thread Dimitry Andric
If you let bsdtar continue, and press control-T a few times, does the user time (u) increase at all? Does it ever go any further, if you let it run for a very long time? I believe a problem may have been introduced by r277922, leading to filesystem hangs in some scenarios. It looks like this

Re: Weird behavior writing to SSD on 2013 MacBook

2015-02-04 Thread Allan Jude
On 2015-02-04 20:40, Lundberg, Johannes wrote: By the way, For the second test I first ran portsnap extract without removing the old /usr/ports folder and it ran through quickly without any halts.. -- Johannes Lundberg BRILLIANTSERVICE CO., LTD. On Thu, Feb 5, 2015 at 10:38 AM,

Re: Weird behavior writing to SSD on 2013 MacBook

2015-02-04 Thread Dimitry Andric
On 05 Feb 2015, at 02:38, Lundberg, Johannes johan...@brilliantservice.co.jp wrote: I deleted /usr/ports and did a new portsnap extract portsnap stopped at /usr/ports/editors/teco that folder is empty and the previous folder (editors/tea) is populated with files. portsnap stopped for