Merge tag 'zonefs-5.6-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/zonefs

+10 -10

1 changed file

expand all

Documentation

filesystems

zonefs.txt

+10 -10

Documentation/filesystems/zonefs.txt

··· 134 134 end, that is, write operations can only be append writes. Zonefs makes no 135 135 attempt at accepting random writes and will fail any write request that has a 136 136 start offset not corresponding to the end of the file, or to the end of the last 137 - write issued and still in-flight (for asynchrnous I/O operations). 137 + write issued and still in-flight (for asynchronous I/O operations). 138 138 139 139 Since dirty page writeback by the page cache does not guarantee a sequential 140 140 write pattern, zonefs prevents buffered writes and writeable shared mappings ··· 142 142 zonefs relies on the sequential delivery of write I/O requests to the device 143 143 implemented by the block layer elevator. An elevator implementing the sequential 144 144 write feature for zoned block device (ELEVATOR_F_ZBD_SEQ_WRITE elevator feature) 145 - must be used. This type of elevator (e.g. mq-deadline) is the set by default 145 + must be used. This type of elevator (e.g. mq-deadline) is set by default 146 146 for zoned block devices on device initialization. 147 147 148 148 There are no restrictions on the type of I/O used for read operations in ··· 196 196 may still happen in the case of a partial failure of a very large direct I/O 197 197 operation split into multiple BIOs/requests or asynchronous I/O operations. 198 198 If one of the write request within the set of sequential write requests 199 - issued to the device fails, all write requests after queued after it will 199 + issued to the device fails, all write requests queued after it will 200 200 become unaligned and fail. 201 201 202 202 * Delayed write errors: similarly to regular block devices, if the device side ··· 207 207 causing all data to be dropped after the sector that caused the error. 208 208 209 209 All I/O errors detected by zonefs are notified to the user with an error code 210 - return for the system call that trigered or detected the error. The recovery 210 + return for the system call that triggered or detected the error. The recovery 211 211 actions taken by zonefs in response to I/O errors depend on the I/O type (read 212 212 vs write) and on the reason for the error (bad sector, unaligned writes or zone 213 213 condition change). ··· 222 222 * A zone condition change to read-only or offline also always triggers zonefs 223 223 I/O error recovery. 224 224 225 - Zonefs minimal I/O error recovery may change a file size and a file access 225 + Zonefs minimal I/O error recovery may change a file size and file access 226 226 permissions. 227 227 228 228 * File size changes: ··· 237 237 A file size may also be reduced to reflect a delayed write error detected on 238 238 fsync(): in this case, the amount of data effectively written in the zone may 239 239 be less than originally indicated by the file inode size. After such I/O 240 - error, zonefs always fixes a file inode size to reflect the amount of data 240 + error, zonefs always fixes the file inode size to reflect the amount of data 241 241 persistently stored in the file zone. 242 242 243 243 * Access permission changes: ··· 281 281 permissions to read-only applies to all files. The file system is remounted 282 282 read-only. 283 283 * Access permission and file size changes due to the device transitioning zones 284 - to the offline condition are permanent. Remounting or reformating the device 284 + to the offline condition are permanent. Remounting or reformatting the device 285 285 with mkfs.zonefs (mkzonefs) will not change back offline zone files to a good 286 286 state. 287 287 * File access permission changes to read-only due to the device transitioning 288 - zones to the read-only condition are permanent. Remounting or reformating 288 + zones to the read-only condition are permanent. Remounting or reformatting 289 289 the device will not re-enable file write access. 290 290 * File access permission changes implied by the remount-ro, zone-ro and 291 291 zone-offline mount options are temporary for zones in a good condition. ··· 301 301 302 302 zonefs define the "errors=<behavior>" mount option to allow the user to specify 303 303 zonefs behavior in response to I/O errors, inode size inconsistencies or zone 304 - condition chages. The defined behaviors are as follow: 304 + condition changes. The defined behaviors are as follow: 305 305 * remount-ro (default) 306 306 * zone-ro 307 307 * zone-offline 308 308 * repair 309 309 310 - The I/O error actions defined for each behavior is detailed in the previous 310 + The I/O error actions defined for each behavior are detailed in the previous 311 311 section. 312 312 313 313 Zonefs User Space Tools

Configure Feed

Configure Feed