http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2360 <pre>It's a 3TB harddisk. Could that be the reason? Right now, it's mounted read-only. Is it safe to make it read/write again? And can I run nilfs-clean on it and maybe the error would be gone? On Sat, May 26, 2012 at 2:06 AM, Reinoud Zandijk &lt;reinoud-S783fYmB3Ccdnm+yROfE0A&lt; at &gt;public.gmane.org&gt; wrote: -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&lt; at &gt;public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Kenneth Langga 2012-05-25T18:15:41 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2359 <pre>Hi Kenneth. On Fri, May 25, 2012 at 10:30:40PM +0800, Kenneth Langga wrote: What struck me is the very high level and the absurt number of number of children. That can't be good. AFAIR NiLFS only has say upto 3 (or 4?) levels in its B-tree. It *could* be failing in rebalancing or more likely pointing to garbage? Cheers, Reinoud -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&lt; at &gt;public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Reinoud Zandijk 2012-05-25T18:06:49 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2358 <pre>I got this error from kernel.log: NILFS: bad btree node (blocknr=111560943): level = 242, flags = 0x3f, nchildren = 23369 NILFS error (device sdc2): nilfs_bmap_lookup_contig: broken bmap (inode number=19696) What is the correct course of action for this type of error? And what would have caused this? -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&lt; at &gt;public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Kenneth Langga 2012-05-25T14:30:40 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2357 <pre>Hi, I suggest to add comment with more details about description of data and b-tree intermediate blocks of the DAT meta-data file in on-disk segment summary. I think that absence of such comment can lead to misunderstanding of segment summary's on-disk layout. With the best regards, Vyacheslav Dubeyko. -- From: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; Subject: [PATCH 1/1] nilfs2: add detailed comment about description of DAT meta-data file's blocks in on-disk segment summary This patch adds comment with more details about description of data and b-tree intermediate blocks of the DAT meta-data file in on-disk segment summary. Signed-off-by: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; --- include/linux/nilfs2_fs.h | 13 ++++++++++++- 1 files changed, 12 insertions(+), 1 deletions(-) diff --git a/include/linux/nilfs2_fs.h b/include/linux/nilfs2_fs.h index 655213e..630f550 100644 --- a/include/linux/nilfs2_fs.h +++ b/include/linux/nilfs2_fs.h &lt; at &gt;&lt; at &gt; -372,7 +37</pre> Vyacheslav Dubeyko 2012-05-24T12:22:03 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2356 <pre> Thanks. I will pick it up. Ryusuke Konishi -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&lt; at &gt;public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Ryusuke Konishi 2012-05-23T13:22:48 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2355 <pre>Hi, I found that ns_mount_state field doesn't commented in the_nilfs structure. I simply add comment for ns_mount_state field. With the best regards, Vyacheslav Dubeyko. -- From: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; Subject: [PATCH 1/1] nilfs2: add omitted comment for ns_mount_state field of the_nilfs structure This patch adds omitted comment for ns_mount_state field of the_nilfs structure. Signed-off-by: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; --- diff --git a/fs/nilfs2/the_nilfs.h b/fs/nilfs2/the_nilfs.h index 1a588a3..7885bdb 100644 --- a/fs/nilfs2/the_nilfs.h +++ b/fs/nilfs2/the_nilfs.h &lt; at &gt;&lt; at &gt; -53,6 +53,7 &lt; at &gt;&lt; at &gt; enum { * &lt; at &gt;ns_sbwtime: previous write time of super block * &lt; at &gt;ns_sbwcount: write count of super block * &lt; at &gt;ns_sbsize: size of valid data in super block + * &lt; at &gt;ns_mount_state: file system state * &lt; at &gt;ns_seg_seq: segment sequence counter * &lt; at &gt;ns_segnum: index number of the latest full segment. * &lt; at &gt;ns_nextnum: index number of the full segment inde</pre> Vyacheslav Dubeyko 2012-05-22T14:25:15 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2354 <pre>Hi Vyacheslav, On Sun, May 20, 2012 at 06:23:29PM +0400, Vyacheslav Dubeyko wrote: Looks good. The byte code examples i'd leave out; they are confusing. Maybe as an edditional part? Cheers, Reinoud -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&lt; at &gt;public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Reinoud Zandijk 2012-05-20T15:50:46 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2353 <pre>Hi Reinoud, On Sun, 2012-05-20 at 17:50 +0200, Reinoud Zandijk wrote: Ok. I see. I will think about it and try to rework. Thank you. With the best regards, Vyacheslav Dubeyko. -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&lt; at &gt;public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Vyacheslav Dubeyko 2012-05-21T05:36:26 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2352 <pre>Hi all, I am working on NILFS2 design doc now. Currently, I elaborated draft of the on-disk layout description paragraph. You can download draft of the design document from here: http://dubeyko.com/development/FileSystems/NILFS/nilfs2-design.pdf. Could you please review the draft of the on-disk layout description paragraph and point out any misunderstandings or misspellings? Thank you in advance. With the best regards, Vyacheslav Dubeyko.-- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&lt; at &gt;public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Vyacheslav Dubeyko 2012-05-20T14:23:29 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2351 <pre>Our Streaming Server is powerful and optimized server for live and on-demand audio/ video streaming content delivery. Our Streaming Server features with high performance streaming throughput, network &amp; storage I/O and optimized configurations for its high scalability and reliability. Our server supports latest Windows Media Technologies such as Fast Streaming, Fast Cache, Fast Start, Wireless Streaming as well as feature-rich add-on modules such as sophisticated content management, monitoring, logging reports, billing, authentications, load-balancing &amp; clustering for all needs. Pls send us email for further information.Thanks, Boris boris-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0&lt; at &gt;public.gmane.org If you do not wish to further receive this event message, email "borislamsv2-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org" to unsubscribe this message or remove your email from the list. -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&lt; at &gt;p</pre> boris-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0< at >public.gmane.org 2012-05-15T19:35:20 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2350 <pre>haalloo, how are you doing,i hope you are fine,my name is miss abi okom i got your contact and want us to be a good friend, please try and write back to me so that i will give you my pictures and tell you more about me, -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&lt; at &gt;public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> abi 2012-05-12T17:06:50 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2349 <pre>Using "-b 1024 -B 512", we would get 512 blocks per segment: (1024*512) / 1024 Then, what about to use "-B" to 1024 or to 2048 ? So there were lesser number of full segments in the device. -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&lt; at &gt;public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Zeke Rondel 2012-05-10T18:01:55 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2348 <pre>Hi, On Thu, 10 May 2012 00:33:30 +0100, Zeke Rondel wrote: Basically NILFS is not designed for small devices. Its most on-disk data items have 64-bit width. In addition, it's more likely to suffer from disk full on such devices due to the copy-on-write nature. However, I guess you can use NILFS on 64MB SD card by formatting the device with a smaller block size and a smaller number of blocks per segment. My mkfs format parameter for a 64MB sized device is as follows: $ mkfs -t nilfs2 -b 1024 -B 512 &lt;device&gt; We may get more disk space overhead for much smaller "blocks per segment" because every segment of NILFS needs at least one header block. Regards, Ryusuke Konishi -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&lt; at &gt;public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Ryusuke Konishi 2012-05-10T15:42:22 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2347 <pre>hi I am trying to test xfstests on nilfs.During this i got this error fsck.nilfs2 not found. Is any one tried xfstests for nilfs and facing same problem ? thanks, karunakar. On Wed, May 9, 2012 at 4:51 PM, Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; wrote: -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&lt; at &gt;public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> karunakar merugu 2012-05-10T05:45:16 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2346 <pre>Hi, I've a small memory card (SD) of 64MB used for keys related to crypto. stuff so I need a log filesystem that avoids the data can be re-written or modified. Is NILFS suitable in case of little devices? If so, which size of blocks per segment would be suitable for it? Thanks in advance! -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&lt; at &gt;public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Zeke Rondel 2012-05-09T23:33:30 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2345 <pre>Hi, Sorry, but as I know fsck tool for NILFS filesystem doesn't implemented yet. With the best regards, Vyacheslav Dubeyko. On May 9, 2012, at 1:16 PM, karunakar merugu wrote: -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&lt; at &gt;public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Vyacheslav Dubeyko 2012-05-09T11:21:37 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2344 <pre>Hi I am using Linux karunakar-VirtualBox 3.0.0-12-generic #20-Ubuntu SMP. I installed nilfs utilities by sudo apt-get update sudo apt-get install nilfs2-tools Even after this I am getting error like: fsck from util-linux 2.19.1 fsck: fsck.nilfs2: not found fsck: Error 2 while executing fsck.nilfs2 for /dev/sdb can anyone help me in finding the correct package for fsck.nilfs2 utility please. thanks, Karunakar. -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&lt; at &gt;public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> karunakar merugu 2012-05-09T09:16:00 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2343 <pre> Thanks for the patch. But, No, the current mkfs implementation is correct. nilfs_binfo_dat is the structure storing summary information only applied to btree intermediate blocks of the DAT meta-data file. For data blocks of the DAT file, a 64-bit block offset number (__le64) is allocated per block. Since mkfs.nilfs2 only allocates data blocks in the initial format and never allocates btree node blocks, nilfs_binfo_dat structure will not appear in the tool. The current kernel module is using the same binfo format. If this patch is applied, compatibility of the disk format will be broken. Regards, Ryusuke Konishi -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&lt; at &gt;public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html </pre> Ryusuke Konishi 2012-05-06T18:29:29 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2342 <pre>Hello, I think that I have found obsolete code in mkfs.nilfs2. And I prepare a patch which fixes the bug with block info initialization in segment summary for the case of DAT file. With the best regards, Vyacheslav Dubeyko. -- From: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; Subject: [PATCH 1/1] mkfs.nilfs2: initialize block info array for DAT file by nilfs_binfo_dat structure Segment summary block begins from segment summary header (nilfs_segment_summary structure). It follows array of file information items (nilfs_finfo structure) after it. And after each file information item follows array of block information items (nilfs_binfo union). The block information item can be nilfs_binfo_v structure (information for the block to which a virtual block number is assigned) or nilfs_binfo_dat structure (information for the block which belongs to the DAT file). Current state of mkfs.nilfs2 code initializes block information items as sizeof(__le64) for the DAT file case. But driver code ex</pre> Vyacheslav Dubeyko 2012-05-06T12:06:41 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2341 <pre>Hi Andrew, Could you please queue the following patch in the -mm tree ? I hope this will be sent to upstream at the next merge window through your tree. (probably only this single change). Thanks, Ryusuke Konishi -- From: Ryusuke Konishi &lt;konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg&lt; at &gt;public.gmane.org&gt; There are two cases that the cache flush is needed to avoid data loss against unexpected hang or power failure. One is sync file function (i.e. nilfs_sync_file) and another is checkpointing ioctl. This issues a cache flush request to device for such cases if barrier mount option is enabled, and makes sure data really is on persistent storage on their completion. Signed-off-by: Ryusuke Konishi &lt;konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg&lt; at &gt;public.gmane.org&gt; --- fs/nilfs2/file.c | 24 ++++++++++++++---------- fs/nilfs2/ioctl.c | 8 +++++++- 2 files changed, 21 insertions(+), 11 deletions(-) diff --git a/fs/nilfs2/file.c b/fs/nilfs2/file.c index 2660152..62cebc8 100644 --- a/fs/nilfs2/file.c +++ b/fs/nilfs2/file.</pre> Ryusuke Konishi 2012-05-05T15:30:19 http://permalink.gmane.org/gmane.comp.file-systems.nilfs.user/2340 <pre>Hi, I'm original author of the grub2 NILFS2 module. Yes, it lacks roll back/forward or recovery to keep the boot loader simple. It also prevent from unintentional boot, like old buggy kernel is used. Aside from the way it works, the code itself is capable to boot from any checkpoints. It happens to choose the latest one. The only thing we need is the way to _choose_ the checkpoint from grub interface :(. thanks regards </pre> Jiro SEKIBA 2012-05-04T05:13:46 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.file-systems.nilfs.user