Martin Steigerwald posted on Sun, 15 Jun 2014 23:31:07 +0200 as excerpted:
> I always thought that the whole point of fallocate is that it *doesn´t*
> write out anything, but just reserves the space. Thus I don´t see how
> COW can have any adverse effect here.
Tying up loose ends... I was wrong
On Sun, Jun 15, 2014 at 11:45:37PM +0200, Martin Steigerwald wrote:
> Am Samstag, 14. Juni 2014, 12:59:31 schrieb Kai Krakow:
> > Well, how did I accomblish that?
>
> Setting no cow and defragmenting regularily?
>
> Quite a complex setup for a casual Linux user.
>
> Any solution should be automa
Am Samstag, 14. Juni 2014, 12:59:31 schrieb Kai Krakow:
> Well, how did I accomblish that?
Setting no cow and defragmenting regularily?
Quite a complex setup for a casual Linux user.
Any solution should be automatic. I´d suggest by a combination of sane
application behaviour and measures within
On Sun, Jun 15, 2014 at 11:31:07PM +0200, Martin Steigerwald wrote:
> Am Samstag, 14. Juni 2014, 02:53:20 schrieb Duncan:
> > > I am reaching the conclusion that fallocate is not the problem. The
> > > fallocate increase the filesize of about 8MB, which is enough for some
> > > logging. So it is no
Am Samstag, 14. Juni 2014, 02:53:20 schrieb Duncan:
> > I am reaching the conclusion that fallocate is not the problem. The
> > fallocate increase the filesize of about 8MB, which is enough for some
> > logging. So it is not called very often.
>
> But...
>
> If a file isn't (properly[1]) set NOC
Duncan <1i5t5.dun...@cox.net> schrieb:
>> Back to the extents counts: What I did next was implementing a defrag
>> job that regularly defrags the journal (actually, the complete log
>> directory as other log files suffer the same problem):
>>
>> $ cat /usr/local/sbin/defrag-logs.rb #!/bin/sh exec
Goffredo Baroncelli posted on Sat, 14 Jun 2014 09:52:39 +0200 as
excerpted:
> On 06/14/2014 04:53 AM, Duncan wrote:
>> Goffredo Baroncelli posted on Sat, 14 Jun 2014 00:19:31 +0200 as
>> excerpted:
>>
>>> thanks for pointing that. However I am performing my tests on a fedora
>>> 20 with systemd-2
Kai Krakow posted on Sat, 14 Jun 2014 12:59:31 +0200 as excerpted:
> Duncan <1i5t5.dun...@cox.net> schrieb:
>
>> As they say, "Whoosh!"
>>
>> At least here, I interpreted that remark as primarily sarcastic
>> commentary on the systemd devs' apparent attitude, which can be
>> (controversially) su
Duncan <1i5t5.dun...@cox.net> schrieb:
> As they say, "Whoosh!"
>
> At least here, I interpreted that remark as primarily sarcastic
> commentary on the systemd devs' apparent attitude, which can be
> (controversially) summarized as: "Systemd doesn't have problems because
> it's perfect. Therefor
On 06/14/2014 04:53 AM, Duncan wrote:
> Goffredo Baroncelli posted on Sat, 14 Jun 2014 00:19:31 +0200 as
> excerpted:
>
>> On 06/13/2014 01:24 AM, Dave Chinner wrote:
>>> On Thu, Jun 12, 2014 at 12:37:13PM +, Duncan wrote:
FWIW, either 4 byte or 8 MiB fallocate calls would be bad, I
Goffredo Baroncelli posted on Sat, 14 Jun 2014 00:19:31 +0200 as
excerpted:
> On 06/13/2014 01:24 AM, Dave Chinner wrote:
>> On Thu, Jun 12, 2014 at 12:37:13PM +, Duncan wrote:
>>>
>>> FWIW, either 4 byte or 8 MiB fallocate calls would be bad, I think
>>> actually pretty much equally bad witho
Hi Dave
On 06/13/2014 01:24 AM, Dave Chinner wrote:
> On Thu, Jun 12, 2014 at 12:37:13PM +, Duncan wrote:
>> Goffredo Baroncelli posted on Thu, 12 Jun 2014
>> 13:13:26 +0200 as excerpted:
>>
systemd has a very stupid journal write pattern. It checks if there is
space in the file for
On Thu, Jun 12, 2014 at 12:37:13PM +, Duncan wrote:
> Goffredo Baroncelli posted on Thu, 12 Jun 2014
> 13:13:26 +0200 as excerpted:
>
> >>systemd has a very stupid journal write pattern. It checks if there is
> >>space in the file for the write, and if not it fallocates the small
> >>amount o
Goffredo Baroncelli posted on Thu, 12 Jun 2014
13:13:26 +0200 as excerpted:
>>systemd has a very stupid journal write pattern. It checks if there is
>>space in the file for the write, and if not it fallocates the small
>>amount of space it needs (it does *4 byte* fallocate calls!) and then
>>does
>Da: da...@fromorbit.com
>Data: 12/06/2014 3.21
>A:
>Cc: "systemd Mailing List", "linux-btrfs"
>Ogg: Re: Slow startup of systemd-journal on BTRFS
>
>On Wed, Jun 11, 2014 at 11:28:54PM +0200, Goffredo Baroncelli wrote:
>> Hi all,
>>
>>
>Messaggio originale
>Da: russ...@coker.com.au
>Data: 12/06/2014 3.18
>A:
>Cc: "systemd Mailing List", "linux-btrfs"
>Ogg: Re: Slow startup of systemd-journal on BTRFS
>
>On Wed, 11 Jun 2014 23:28:54 Goffredo Baroncelli wrote:
>>
>Messaggio originale
>Da: li...@colorremedies.com
>Data: 12/06/2014 2.40
>A: , "Goffredo Baroncelli"
>Cc: "systemd Mailing List", "linux-btrfs"
>Ogg: Re: Slow startup of systemd-journal on BTRFS
>
>
>On Jun 11, 2014, at 3:28 PM,
Russell Coker posted on Thu, 12 Jun 2014 11:18:37 +1000 as excerpted:
> On Wed, 11 Jun 2014 23:28:54 Goffredo Baroncelli wrote:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1006386
>>
>> suggested me that the problem could be due to a bad interaction between
>> systemd and btrfs. Networ
On Jun 11, 2014, at 7:21 PM, Dave Chinner wrote:
> On Wed, Jun 11, 2014 at 11:28:54PM +0200, Goffredo Baroncelli wrote:
>> Hi all,
>>
>> I would like to share a my experience about a slowness of systemd when used
>> on BTRFS.
>>
>> My boot time was very high (about ~50 seconds); most of time i
On Thu, Jun 12, 2014 at 11:21:04AM +1000, Dave Chinner wrote:
> On Wed, Jun 11, 2014 at 11:28:54PM +0200, Goffredo Baroncelli wrote:
> > Hi all,
> >
> > I would like to share a my experience about a slowness of systemd when used
> > on BTRFS.
> >
> > My boot time was very high (about ~50 seconds
On Wed, Jun 11, 2014 at 11:28:54PM +0200, Goffredo Baroncelli wrote:
> Hi all,
>
> I would like to share a my experience about a slowness of systemd when used
> on BTRFS.
>
> My boot time was very high (about ~50 seconds); most of time it was due to
> NetworkManager which took about 30-40 secon
On Wed, 11 Jun 2014 23:28:54 Goffredo Baroncelli wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1006386
>
> suggested me that the problem could be due to a bad interaction between
> systemd and btrfs. NetworkManager was innocent. It seems that
> systemd-journal create a very hight f
On Jun 11, 2014, at 3:28 PM, Goffredo Baroncelli wrote:
>
> If someone is able to suggest me how FRAGMENT the log file, I can try to
> collect more scientific data.
So long as you're not using compression, filefrag will show you fragments of
systemd-journald journals. I can vouch for the beha
23 matches
Mail list logo
