Searched hist:"7 d8f9f7d" (Results 1 – 3 of 3) sorted by relevance
/openbmc/linux/fs/ext4/ |
H A D | file.c | 7d8f9f7d Tue Feb 24 07:21:14 CST 2009 Theodore Ts'o <tytso@mit.edu> ext4: Automatically allocate delay allocated blocks on close
When closing a file that had been previously truncated, force any delay allocated blocks that to be allocated so that if the filesystem is mounted with data=ordered, the data blocks will be pushed out to disk along with the journal commit. Many application programs expect this, so we do this to avoid zero length files if the system crashes unexpectedly.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> 7d8f9f7d Tue Feb 24 07:21:14 CST 2009 Theodore Ts'o <tytso@mit.edu> ext4: Automatically allocate delay allocated blocks on close When closing a file that had been previously truncated, force any delay allocated blocks that to be allocated so that if the filesystem is mounted with data=ordered, the data blocks will be pushed out to disk along with the journal commit. Many application programs expect this, so we do this to avoid zero length files if the system crashes unexpectedly. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
|
H A D | ext4.h | 7d8f9f7d Tue Feb 24 07:21:14 CST 2009 Theodore Ts'o <tytso@mit.edu> ext4: Automatically allocate delay allocated blocks on close
When closing a file that had been previously truncated, force any delay allocated blocks that to be allocated so that if the filesystem is mounted with data=ordered, the data blocks will be pushed out to disk along with the journal commit. Many application programs expect this, so we do this to avoid zero length files if the system crashes unexpectedly.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> 7d8f9f7d Tue Feb 24 07:21:14 CST 2009 Theodore Ts'o <tytso@mit.edu> ext4: Automatically allocate delay allocated blocks on close When closing a file that had been previously truncated, force any delay allocated blocks that to be allocated so that if the filesystem is mounted with data=ordered, the data blocks will be pushed out to disk along with the journal commit. Many application programs expect this, so we do this to avoid zero length files if the system crashes unexpectedly. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
|
H A D | inode.c | 7d8f9f7d Tue Feb 24 07:21:14 CST 2009 Theodore Ts'o <tytso@mit.edu> ext4: Automatically allocate delay allocated blocks on close
When closing a file that had been previously truncated, force any delay allocated blocks that to be allocated so that if the filesystem is mounted with data=ordered, the data blocks will be pushed out to disk along with the journal commit. Many application programs expect this, so we do this to avoid zero length files if the system crashes unexpectedly.
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> 7d8f9f7d Tue Feb 24 07:21:14 CST 2009 Theodore Ts'o <tytso@mit.edu> ext4: Automatically allocate delay allocated blocks on close When closing a file that had been previously truncated, force any delay allocated blocks that to be allocated so that if the filesystem is mounted with data=ordered, the data blocks will be pushed out to disk along with the journal commit. Many application programs expect this, so we do this to avoid zero length files if the system crashes unexpectedly. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
|