diff options
author | Artem Bityutskiy <artem.bityutskiy@linux.intel.com> | 2013-03-14 09:49:23 +0100 |
---|---|---|
committer | Artem Bityutskiy <artem.bityutskiy@linux.intel.com> | 2013-03-14 10:20:22 +0100 |
commit | 67e753ca41782913d805ff4a8a2b0f60b26b7915 (patch) | |
tree | b7a7e8a033fdc6427f42c320c0b6f12628bdd8ac /fs/namespace.c | |
parent | Linux 3.9-rc2 (diff) | |
download | linux-67e753ca41782913d805ff4a8a2b0f60b26b7915.tar.xz linux-67e753ca41782913d805ff4a8a2b0f60b26b7915.zip |
UBIFS: make space fixup work in the remount case
The UBIFS space fixup is a useful feature which allows to fixup the "broken"
flash space at the time of the first mount. The "broken" space is usually the
result of using a "dumb" industrial flasher which is not able to skip empty
NAND pages and just writes all 0xFFs to the empty space, which has grave
side-effects for UBIFS when UBIFS trise to write useful data to those empty
pages.
The fix-up feature works roughly like this:
1. mkfs.ubifs sets the fixup flag in UBIFS superblock when creating the image
(see -F option)
2. when the file-system is mounted for the first time, UBIFS notices the fixup
flag and re-writes the entire media atomically, which may take really a lot
of time.
3. UBIFS clears the fixup flag in the superblock.
This works fine when the file system is mounted R/W for the very first time.
But it did not really work in the case when we first mount the file-system R/O,
and then re-mount R/W. The reason was that we started the fixup procedure too
late, which we cannot really do because we have to fixup the space before it
starts being used.
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Reported-by: Mark Jackson <mpfj-list@mimc.co.uk>
Cc: stable@vger.kernel.org # 3.0+
Diffstat (limited to 'fs/namespace.c')
0 files changed, 0 insertions, 0 deletions