diff options
| author | Jiro SEKIBA <jir@unicus.jp> | 2010-05-02 23:29:04 +0900 |
|---|---|---|
| committer | Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp> | 2010-05-10 11:32:33 +0900 |
| commit | 400ade845cb9930552e791bbd658a0953f68499d (patch) | |
| tree | 169526937ed5d61092680328a2ee1ba4b5221fe9 /fs/direct-io.c | |
| parent | 25294d8c376296b1420694317e9856eaaea710ca (diff) | |
nilfs2: enlarge s_volume_name member in nilfs_super_block
Current s_volume_name has 16 bytes, which is too small as modern filesystem.
s_last_mounted resides just after s_volume_name and has 64 bytes.
s_last_mounted is historically came from ext2, but not used in nilfs2 at all.
Deleting s_last_mounted member and merging that space with s_volume_name
enlarge s_volume_name upto 80 bytes for volume label.
When user land tools see the old header for new disk, it will just ignore
additional bytes stored in s_last_mounted. While, old disk format has only
16 bytes label, it doesn't affects in case seeing the new header for old disk.
Signed-off-by: Jiro SEKIBA <jir@unicus.jp>
Signed-off-by: Ryusuke Konishi <konishi.ryusuke@lab.ntt.co.jp>
Diffstat (limited to 'fs/direct-io.c')
0 files changed, 0 insertions, 0 deletions