dimas wrote: > that sounds good! but as i remember, you've mentioned some issues about 2.6.35 > earlier, which were to be fixed. among them there was the troble with loop > devices. how about this? yes, this has been fixed in .36 > and there was a mail here where author complained about > problems after moving from 34 to 35. is 36 version more stable or it is better > to still rely on 34.7, which works nice for me? > I think that moving to .36 is a must, however I don't test released stuff well enough, so, please keep a possibility to roll back to previous stuff and report, if any problems. > Edward Shishkin ÐÐÑÐÑ: > >> Changes since 2.6.35: >> >> . Fixed ->write_end() method: the old one didn't update i_size, and this >> resulted in empty files and "orphan" items. The problem took place only >> for splice users (loop devices, pipe2, etc). >> >> . Implemented ->sync_fs() method of super operations. Since introducing a >> new per-bdi flushing stuff reiser4 wasn't able to perform sync on umount. >> Now such sync is performed by reiser4_sync_fs(). >> >> . Fixed an old bug which led to non-deletable directories. >> >> . Fixed an old bug in tail conversion, which led to data corruption when >> running in disk space pressure situations. >> >> Please, find at >> http://www.kernel.org/pub/linux/kernel/people/edward/reiser4/reiser4-for-2.6/ >> > > -- To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
