Received-SPF: pass (google.com: domain of linux-ext4-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <CAMU1PDgNvW_3Jr91iii-Nh=DCuRytVG8ka3-J+a43gKwigx8Yg@mail.gmail.com>
 <34ca4e40-2026-d48d-7181-fbea6ba4f140@thelounge.net>
In-Reply-To: <34ca4e40-2026-d48d-7181-fbea6ba4f140@thelounge.net>
From:   Mike Fleetwood <mike.fleetwood@googlemail.com>
Date:   Tue, 27 Jul 2021 08:32:53 +0100
Message-ID: <CAMU1PDgJAadK21H_-u3vg0NujKRzBegH0SHL2+54+23ZppFDgQ@mail.gmail.com>
Subject: Re: Is labelling a mounted ext2/3/4 file system safe and supported?
To:     Reindl Harald <h.reindl@thelounge.net>
Cc:     linux-ext4@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Mon, 26 Jul 2021 at 21:50, Reindl Harald <h.reindl@thelounge.net> wrote:
> Am 26.07.21 um 20:45 schrieb Mike Fleetwood:
> > Hi,
> >
> > Using e2label to set a new label for a mounted ext4 seems to work, but
> > is it a safe and supported thing to do?
>
> it is

Is there some documentation which states it's safe to write to the label
while mounted?

I ask because 1) I am looking at adding such support into GParted and
2) I don't understand how it can be safe.

Looking at the e2label source code, it just reads the superblock,
updates the label and writes the super block.  How is that safe and
persistent when presumably the linux kernel has an in-memory copy of the
superblock will be written at unmount and presumable sync.

Thanks,
Mike