| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sat, 16 Oct 2010 01:02:12 -0500 From: Hubert Bahr <hab@...hr.org> To: linux-ext4@...r.kernel.org Subject: extremely long delays are they possible? In reality I would prefer writes only occur to an ssd if the FS write cache is overflowing. The application is package rebuilding. The package is brought in from nfs expanded built (compiled etc) then the results written back to an nfs mount and the log written to Cluster Head then everything erased. However, if there are build problems the expanded file system and results are left intact. My Memory Size is large enough (16GB) to buffer the whole process except when a build problem occur's. Since this can be hours into a build I would prefer to capture. This is part of a cluster batch process that is only examined at the expected end of the total batch process. Capturing the problems precludes using only a ramfs, but I would like to avoid needless writes to the ssd. I am afraid that embedded fsyncs may blow this anyway. Maybe I could use some on error mv but I prefer the dynamic memory sharing rather than a fixed ramfs. The longest single package build I have observed is 11.5 hours and it also took the most space. would fstab options like ext4 commit=50000,noatime,delalloc,data=writeback give me the desired action? Thanks Hubert -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists