On Wed, 2014-01-15 at 11:44 +0100, Clemens Eisserer wrote: > Hi, > > Recently my raspberry pi destroyed a 32GB SD card after only 4 days, > because that cheap SD card seemed to have issues with wear-leveling. > The areas where the ext4 journal was stored were no longer read- or writeable. > > I wonder which write-access patterns nilfs2 does exhibit. > Are there any frequent in-place updates to statically positioned data > structures (superblock, translation tables, ...) or is the data mostly > written sequentially? > The main approach of NILFS2 is COW (copy-on-write) policy. It means that all data and metadata are written in log manner. Only superblocks are placed in fixed positions and updated there. First superblock is located in the volume begin, second one in the volume end. With the best regards, Vyacheslav Dubeyko. > Thank you in advance, Clemens > -- > To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
