bigtreetech / bigtreetech/CB1

/etc/fstab commit vs sync script?

Open
#225 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
496
Forks
86
PR merge metrics
No merged PRs in 30d

Description

Trying to understand why there is a /boot/scripts/sync.sh to call sync every 5 seconds?
```
#!/bin/bash

# regular sync to prevent data loss when direct power outage
while [ 1 ]; do
sync
sleep 5
done
```
Why not set commit parameter in /etc/fstab to 5 instead? Current in v3 seems to be 120s.
`UUID=4a110fbf-cbb4-411f-98a6-77514a52001d / ext4 defaults,noatime,commit=120,errors=remount-ro 0 1`

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with /boot/scripts/sync.sh and the /etc/fstab entry shown in the issue, then trace how the image configures filesystem syncing. Determine the intended rationale for the 5-second sync loop versus commit=120 and document the decision or identify the configuration change maintainers should make.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, shell
Domain
operating-systems
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.