Re: [PATCH] ovl: fix failure to fsync lower dir

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Amir,

Le mercredi 08 novembre 2017, Amir Goldstein a écrit :
> The problem reported by Raphael is that new PostgreSQL 10.0 with a
> database in overlayfs where lower layer in squashfs fails to start.
> The failure is due to fsync error, when PostgreSQL does fsync on all
> existing db directories on startup and a specific directory exists
> lower layer with no changes.

I confirm that this patch is enough to fix my issue.

Tested-by: Raphaël Hertzog <hertzog@xxxxxxxxxx>

I wonder if we can have a similar problem with a file. Is it possible to
fsync a file opened in read-only mode? Even if it's possible, I assume
this is really rare.

And when you open a file with read-write permissions, when does the
copy-up happen? If it's immediately, then fsync on such a file is safe as
well.

Cheers,
-- 
Raphaël Hertzog ◈ Writer/Consultant ◈ Debian Developer

Discover the Debian Administrator's Handbook:
→ https://debian-handbook.info/get/
--
To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Filesystems Devel]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux