Displaying 5 results from an estimated 5 matches for "dirty_background_byt".
Did you mean:
dirty_background_bytes
2015 Jan 06
2
reboot - is there a timeout on filesystem flush?
I've had a few systems with a lot of RAM and very busy filesystems
come up with filesystem errors that took a manual 'fsck -y' after what
should have been a clean reboot. This is particularly annoying on
remote systems where I have to talk someone else through the recovery.
Is there some time limit on the cache write with a 'reboot' (no
options) command or is ext4 that
2015 Jan 07
0
reboot - is there a timeout on filesystem flush?
...hrough the recovery.
>
> Is there some time limit on the cache write with a 'reboot' (no
> options) command or is ext4 that fragile?
I'd say there's no limit in the amount of time the kernel waits until
the blocks have been written to disk; driven by there parameters:
vm.dirty_background_bytes = 0
vm.dirty_background_ratio = 10
vm.dirty_bytes = 0
vm.dirty_expire_centisecs = 3000
vm.dirty_ratio = 20
vm.dirty_writeback_centisecs = 500
ie, if the data cached on RAM is older than 30s or larger than 10%
available RAM, the kernel will try to flush it to disk. Depending how
much data needs t...
2020 Apr 20
4
performance problems with notmuch new
Franz Fellner <alpine.art.de at gmail.com> writes:
> I also suffer from bad performance of notmuch new. I used notmuch
> some years ago and notmuch new always felt instantanious. Had to stop
> using it because internet was too slow to sync my mails :/ Now (with
> better internet and a completely new setup using mbsync) indexing one
> mail takes at least 10 seconds,
2015 Jan 07
5
reboot - is there a timeout on filesystem flush?
...; Is there some time limit on the cache write with a 'reboot' (no
>> options) command or is ext4 that fragile?
>
> I'd say there's no limit in the amount of time the kernel waits until
> the blocks have been written to disk; driven by there parameters:
>
> vm.dirty_background_bytes = 0
> vm.dirty_background_ratio = 10
> vm.dirty_bytes = 0
> vm.dirty_expire_centisecs = 3000
> vm.dirty_ratio = 20
> vm.dirty_writeback_centisecs = 500
>
> ie, if the data cached on RAM is older than 30s or larger than 10%
> available RAM, the kernel will try to flush it...
2013 Dec 30
2
oom situation
...0
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
DirectMap4k: 10232 kB
DirectMap2M: 901120 kB
sysctl:
vm.oom_dump_tasks = 0
vm.oom_kill_allocating_task = 1
vm.panic_on_oom = 1
vm.admin_reserve_kbytes = 8192
vm.block_dump = 0
vm.dirty_background_bytes = 0
vm.dirty_background_ratio = 10
vm.dirty_bytes = 0
vm.dirty_expire_centisecs = 3000
vm.dirty_ratio = 20
vm.dirty_writeback_centisecs = 500
vm.drop_caches = 0
vm.highmem_is_dirtyable = 0
vm.hugepages_treat_as_movable = 0
vm.hugetlb_shm_group = 0
vm.laptop_mode = 0
vm.legacy_va_layout = 0
vm.low...