Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 3 of 3 for Fdatasync (1.12 sec)

  1. cmd/os-instrumented.go

    	defer updateOSMetrics(osMetricCreate, name)(err)
    	return os.Create(name)
    }
    
    // Fdatasync captures time taken to call Fdatasync
    func Fdatasync(f *os.File) (err error) {
    	fn := ""
    	if f != nil {
    		fn = f.Name()
    	}
    	defer updateOSMetrics(osMetricFdatasync, fn)(err)
    	return disk.Fdatasync(f)
    }
    
    // report returns all os metrics.
    func (o *osMetrics) report() madmin.OSMetrics {
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Fri Aug 29 02:39:48 UTC 2025
    - 6.2K bytes
    - Viewed (0)
  2. docs/distributed/README.md

    **In our tests we also found ext4 does not honor POSIX O_DIRECT/Fdatasync semantics, ext4 trades performance for consistency guarantees. Please avoid ext4 in your setup.**
    
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Aug 12 18:20:36 UTC 2025
    - 8.9K bytes
    - Viewed (0)
  3. cmd/xl-storage.go

    	flags := os.O_CREATE | os.O_WRONLY | os.O_TRUNC
    
    	var w *os.File
    	if sync {
    		// Perform DirectIO along with fdatasync for larger xl.meta, mostly when
    		// xl.meta has "inlined data" we prefer writing O_DIRECT and then doing
    		// fdatasync() at the end instead of opening the file with O_DSYNC.
    		//
    		// This is an optimization mainly to ensure faster I/O.
    		if len(b) > xioutil.DirectioAlignSize {
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Fri Jun 13 11:33:47 UTC 2025
    - 91.7K bytes
    - Viewed (0)
Back to top