On Nov 27, 2012, at 6:19 PM, Piotr Szymaniak wrote: > On Sat, Nov 17, 2012 at 10:27:36AM +0900, Ryusuke Konishi wrote: >> On Sat, Nov 17, 2012 at 12:02 AM, <fwdnilfsml.to.11df@xxxxxxxx> wrote: >>>> Hmm, the default value of this parameter is zero. >>>> Have you changed it with the nilfs-tune tool by some chance ? >>> >>> Yes, I've changed it to 60 sec for rootfs partition, and 180 sec for data >>> partition. It worked flawlessly with this setup on root partition for last >>> 14 months... >> >> OK, please confirm version of your all kernels including initrd. > > As I got this issue here's some info: > (nilfs_cleanerd_rootfs.conf that I'm using for rootfs) > protection_period 3600 > min_clean_segments 15% > max_clean_segments 25% > clean_check_interval 10 > selection_policy timestamp # timestamp in ascend order > nsegments_per_clean 2 > mc_nsegments_per_clean 4 > cleaning_interval 5 > mc_cleaning_interval 1 > retry_interval 60 > use_mmap > log_priority info > > maszn ~ (: uname -srm > Linux 3.6.4 i686 > > maszn ~ (: eix nilfs-utils -c > [I] sys-fs/nilfs-utils (2.1.4@12.07.2012): *snip* > > What's the next step to debug this issue? > Could you describe the path of issue reproducing? What filesystem operations took place near before the issue? With the best regards, Vyacheslav Dubeyko. > Piotr Szymaniak. > -- > Jedna z głów Zaphoda spojrzała w bok. Druga zrobiła zaraz to samo, > gdyż chciała zobaczyć, na co patrzy pierwsza, nie było to jednak nic > konkretnego. > -- Douglas Adams, "The Hitchhiker's Guide to the Galaxy" -- 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
