Le mardi 07 novembre 2017, Amir Goldstein a écrit : > > FWIW I reported this fsync() on a non-modified directory to PostgreSQL > > developers here: > > https://www.postgresql.org/message-id/20171107135454.lbelbbvfgadljmuj%40home.ouaza.com > > I guess regardless of what overlayfs behavior should be, PostgreSQL > developers better fix this somehow otherwise postgress upgrade is going to > break for users with stable kernel. Given the current set of answers, it seems unlikely that PostgreSQL will stop doing those fsync() calls on unmodified directories because it's hard for them to track whether the directory is dirty or not but it might start to ignore EINVAL/EROFS errors on those fsync calls. That said I don't think that the number of persons using PostgreSQL on top of overlayfs is so important that they are worried about this breakage pattern on upgrade... 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
