Re: [RFC 0/13] extents and 48bit ext3
Andreas Dilger <[email protected]>
| Newsgroups | gmane.comp.file-systems.ext2.devel,gmane.linux.kernel,gmane.linux.file-systems |
|---|---|
| Message-ID | <[email protected]> |
On Jun 14, 2006 18:45 +0200, Bodo Eggert wrote: > BTW: Upgrading a filesystem by using mount options _and_ forcing that > option to be supplied on subsequent mounts is a BUG. If should be what > current code demands, it should be fixed ASAP. I hope that's not what > the current code does. If you don't remount with "-o extents" all it (currently) means is that new files will not be created with extents. Existing extent-mapped files will continue to work. It was done this way so that if some serious problem was found with extents there was a fallback position to "normal" block mapped files and the damage would be limited to files created while mounted with "-o extents". Cheers, Andreas -- Andreas Dilger Principal Software Engineer Cluster File Systems, Inc.