<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.file-systems.nilfs.user">
    <title>gmane.comp.file-systems.nilfs.user</title>
    <link>http://blog.gmane.org/gmane.comp.file-systems.nilfs.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2358"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2357"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2355"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2352"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2351"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2350"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2346"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2344"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2342"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2341"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2339"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2335"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2334"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2331"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2328"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2327"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2324"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2316"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2315"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2314"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2358">
    <title>NILFS: bad btree node</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2358</link>
    <description>&lt;pre&gt;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&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Kenneth Langga</dc:creator>
    <dc:date>2012-05-25T14:30:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2357">
    <title>[PATCH 1/1] nilfs2: add detailed comment about description of  DAT meta-data file's blocks in on-disk segment summary</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2357</link>
    <description>&lt;pre&gt;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 &amp;lt;slava-yeENwD64cLxBDgjK7y7TUQ&amp;lt; at &amp;gt;public.gmane.org&amp;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 &amp;lt;slava-yeENwD64cLxBDgjK7y7TUQ&amp;lt; at &amp;gt;public.gmane.org&amp;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
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -372,7 +372,18 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; struct nilfs_binfo_v {
 };
 
 /**
- * struct nilfs_binfo_dat - information for the block which belongs to
the DAT file
+ * Description of DAT meta-data file's blocks is a special case of
segment summary.
+ * The description can contain as data blocks as b-tree intermediate
blocks.
+ * The whole number of blocks (including intermediate blocks) is
described
+ * by fi_nblocks field of nilfs_finfo structure. The fi_ndatablk field
keeps
+ * count of data blocks. Firstly, it is described data blocks by means
of
+ * 64-bit block offset number (__le64) which is allocated per block.
+ * Finally, b-tree intermediate blocks are described by nilfs_binfo_dat
+ * structure which is allocated per block.
+ */
+
+/**
+ * struct nilfs_binfo_dat - information for b-tree intermediate block
of the DAT meta-data file
  * &amp;lt; at &amp;gt;bi_blkoff: block offset
  * &amp;lt; at &amp;gt;bi_level: level
  * &amp;lt; at &amp;gt;bi_pad: padding
--


--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Vyacheslav Dubeyko</dc:creator>
    <dc:date>2012-05-24T12:22:03</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2355">
    <title>[PATCH 1/1] nilfs2: add omitted comment for ns_mount_state field of the_nilfs structure</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2355</link>
    <description>&lt;pre&gt;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 &amp;lt;slava-yeENwD64cLxBDgjK7y7TUQ&amp;lt; at &amp;gt;public.gmane.org&amp;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 &amp;lt;slava-yeENwD64cLxBDgjK7y7TUQ&amp;lt; at &amp;gt;public.gmane.org&amp;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
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -53,6 +53,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; enum {
  * &amp;lt; at &amp;gt;ns_sbwtime: previous write time of super block
  * &amp;lt; at &amp;gt;ns_sbwcount: write count of super block
  * &amp;lt; at &amp;gt;ns_sbsize: size of valid data in super block
+ * &amp;lt; at &amp;gt;ns_mount_state: file system state
  * &amp;lt; at &amp;gt;ns_seg_seq: segment sequence counter
  * &amp;lt; at &amp;gt;ns_segnum: index number of the latest full segment.
  * &amp;lt; at &amp;gt;ns_nextnum: index number of the full segment index to be used next
--


--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Vyacheslav Dubeyko</dc:creator>
    <dc:date>2012-05-22T14:25:15</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2352">
    <title>[NILFS2 design doc] draft of the on-disk layout description paragraph</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2352</link>
    <description>&lt;pre&gt;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&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Vyacheslav Dubeyko</dc:creator>
    <dc:date>2012-05-20T14:23:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2351">
    <title>Streaming Service</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2351</link>
    <description>&lt;pre&gt;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;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;amp; clustering for all needs. 

Pls send us email for further information.Thanks,

Boris 
boris-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0&amp;lt; at &amp;gt;public.gmane.org

If you do not wish to further receive this event message, email "borislamsv2-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;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&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>boris-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-05-15T19:35:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2350">
    <title>haalloo,</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2350</link>
    <description>&lt;pre&gt;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&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>abi</dc:creator>
    <dc:date>2012-05-12T17:06:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2346">
    <title>Small device</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2346</link>
    <description>&lt;pre&gt;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&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Zeke Rondel</dc:creator>
    <dc:date>2012-05-09T23:33:30</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2344">
    <title>fsck.nilfs2: not found</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2344</link>
    <description>&lt;pre&gt;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&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>karunakar merugu</dc:creator>
    <dc:date>2012-05-09T09:16:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2342">
    <title>[PATCH 1/1] mkfs.nilfs2: initialize block info array for DAT file by nilfs_binfo_dat structure</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2342</link>
    <description>&lt;pre&gt;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 &amp;lt;slava-yeENwD64cLxBDgjK7y7TUQ&amp;lt; at &amp;gt;public.gmane.org&amp;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 expects greater structure in size because it operates by bi_level field for the case of DAT file. The patch uses nilfs_binfo_dat structure instead of __le64 during creation of block information items for DAT file case.

Signed-off-by: Vyacheslav Dubeyko &amp;lt;slava-yeENwD64cLxBDgjK7y7TUQ&amp;lt; at &amp;gt;public.gmane.org&amp;gt;
---
diff -up nilfs-utils/sbin/mkfs/mkfs.c{.orig,} 
--- nilfs-utils/sbin/mkfs/mkfs.c.orig2012-05-04 12:30:58.308461058 +0400
+++ nilfs-utils/sbin/mkfs/mkfs.c2012-05-04 12:32:39.593861721 +0400
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -444,7 +444,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static void increment_segsum_size(struct
   unsigned nblocks_in_file, int dat_flag)
 {
 unsigned binfo_size = dat_flag ? 
-sizeof(__le64) /* offset */ : sizeof(struct nilfs_binfo_v);
+sizeof(struct nilfs_binfo_dat) : sizeof(struct nilfs_binfo_v);
 
 si-&amp;gt;sumbytes = __increment_segsum_size(si-&amp;gt;sumbytes,
        sizeof(struct nilfs_finfo), 1);
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -1240,13 +1240,13 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static void update_blocknr(struct nilfs_
 finfo-&amp;gt;fi_cno = cpu_to_le64(1);
 
 if (fi-&amp;gt;ino == NILFS_DAT_INO) {
-__le64 *pblkoff;
+struct nilfs_binfo_dat *pbinfo_dat;
 
 fi-&amp;gt;raw_inode-&amp;gt;i_bmap[0] = 0;
 for (i = 0; i &amp;lt; fi-&amp;gt;nblocks; i++) {
-pblkoff = map_segsum_info(start, sum_offset,
-  sizeof(*pblkoff));
-*pblkoff = cpu_to_le64(i);
+pbinfo_dat = map_segsum_info(start, sum_offset,
+  sizeof(*pbinfo_dat));
+pbinfo_dat-&amp;gt;bi_blkoff = cpu_to_le64(i);
 fi-&amp;gt;raw_inode-&amp;gt;i_bmap[i + 1] =
 cpu_to_le64(fi-&amp;gt;start + i);
 }
--

--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Vyacheslav Dubeyko</dc:creator>
    <dc:date>2012-05-06T12:06:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2341">
    <title>[PATCH] nilfs2: flush disk caches in syncing</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2341</link>
    <description>&lt;pre&gt;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 &amp;lt;konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg&amp;lt; at &amp;gt;public.gmane.org&amp;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 &amp;lt;konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg&amp;lt; at &amp;gt;public.gmane.org&amp;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.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -37,6 +37,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; int nilfs_sync_file(struct file *file, loff_t start, loff_t end, int datasync)
  * This function should be implemented when the writeback function
  * will be implemented.
  */
+struct the_nilfs *nilfs;
 struct inode *inode = file-&amp;gt;f_mapping-&amp;gt;host;
 int err;
 
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -45,18 +46,21 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; int nilfs_sync_file(struct file *file, loff_t start, loff_t end, int datasync)
 return err;
 mutex_lock(&amp;amp;inode-&amp;gt;i_mutex);
 
-if (!nilfs_inode_dirty(inode)) {
-mutex_unlock(&amp;amp;inode-&amp;gt;i_mutex);
-return 0;
+if (nilfs_inode_dirty(inode)) {
+if (datasync)
+err = nilfs_construct_dsync_segment(inode-&amp;gt;i_sb, inode,
+    0, LLONG_MAX);
+else
+err = nilfs_construct_segment(inode-&amp;gt;i_sb);
 }
-
-if (datasync)
-err = nilfs_construct_dsync_segment(inode-&amp;gt;i_sb, inode, 0,
-    LLONG_MAX);
-else
-err = nilfs_construct_segment(inode-&amp;gt;i_sb);
-
 mutex_unlock(&amp;amp;inode-&amp;gt;i_mutex);
+
+nilfs = inode-&amp;gt;i_sb-&amp;gt;s_fs_info;
+if (!err &amp;amp;&amp;amp; nilfs_test_opt(nilfs, BARRIER)) {
+err = blkdev_issue_flush(inode-&amp;gt;i_sb-&amp;gt;s_bdev, GFP_KERNEL, NULL);
+if (err != -EIO)
+err = 0;
+}
 return err;
 }
 
diff --git a/fs/nilfs2/ioctl.c b/fs/nilfs2/ioctl.c
index 2a70fce..06658ca 100644
--- a/fs/nilfs2/ioctl.c
+++ b/fs/nilfs2/ioctl.c
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -692,8 +692,14 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; static int nilfs_ioctl_sync(struct inode *inode, struct file *filp,
 if (ret &amp;lt; 0)
 return ret;
 
+nilfs = inode-&amp;gt;i_sb-&amp;gt;s_fs_info;
+if (nilfs_test_opt(nilfs, BARRIER)) {
+ret = blkdev_issue_flush(inode-&amp;gt;i_sb-&amp;gt;s_bdev, GFP_KERNEL, NULL);
+if (ret == -EIO)
+return ret;
+}
+
 if (argp != NULL) {
-nilfs = inode-&amp;gt;i_sb-&amp;gt;s_fs_info;
 down_read(&amp;amp;nilfs-&amp;gt;ns_segctor_sem);
 cno = nilfs-&amp;gt;ns_cno - 1;
 up_read(&amp;amp;nilfs-&amp;gt;ns_segctor_sem);
&lt;/pre&gt;</description>
    <dc:creator>Ryusuke Konishi</dc:creator>
    <dc:date>2012-05-05T15:30:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2339">
    <title>Server Rental Service in Hong Kong</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2339</link>
    <description>&lt;pre&gt;Dear All,

We have our own datacenter in Hong Kong &amp;amp; provide email/application/web rental service to clients.We are APNIC member &amp;amp; provide clean IP to clients.

Dell? PowerEdge? EnterpriseRack Mount Server
-Intel(R) Xeon(R) E3-1240 Processor (3.3GHz, 8M Cache, Turbo, 4C/8T, 80W)
-8GB RAM, 2x4GB, 1333MHz, DDR-3, Dual Ranked UDIMMs
-500GB, 3.5", 6Gbps SAS x 2
-Raid 1 Mirroring Protection
-Remote KVM (iDRAC6 Enterprise)

Dell(TM) PowerEdge(TM) R410 Rack Mount Server
-Intel(R) Quad Core E5606 Xeon(R) CPU, 2.13GHz, 4M Cache, 4.86 GT/s QPI
-4GB Memory (2x2GB), 1333MHz Dual Ranked RDIMMs Fully-Buffered
-500GB 7.2K RPM SATAII 3.5" Hard Drive x 2
-iDRAC6 Enterprise or Express (Remote KVM Management)

Every Dedicated Server Hosting Solution Also Includes: 
 
Software Specification 
- CentOS / Fedora / Debian / FreeBSD / Ubuntu / Redhat Linux 
- Full root-level access 
- Data Center Facilities 
- Shared Local &amp;amp; International Bandwidth 
- 2 IP Addresses Allocation 
- Un-interruptible Power Supply (UPS) backed up by private diesel generator 
- FM200¡§based fire suppression system 
- 24x7 CRAC Air Conditioning and Humidity Control 
- 24x7 Security Control 
- 24x7 Remote Hand Service 

Pls send us email for further information.Thanks,

Boris 
boris-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0&amp;lt; at &amp;gt;public.gmane.org

If you do not wish to further receive this event message, email "borislamsv2-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;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&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>boris-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-05-03T18:25:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2335">
    <title>man nilfs-clean</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2335</link>
    <description>&lt;pre&gt;Hi all.

First of all let me thank and congratulate everyone on the nilfs2 project.

I believe I found a typo in the nilfs-clean man page. (is an interger
value -&amp;gt; is an integer value)
I cloned the git repo, edited the file and then I did a git diff.
Not sure if this is the proper way to post a "patch" but here's my first try.

diff --git a/man/nilfs-clean.8 b/man/nilfs-clean.8
index 758b9e1..04e11c6 100644
--- a/man/nilfs-clean.8
+++ b/man/nilfs-clean.8
&amp;lt; at &amp;gt;&amp;lt; at &amp;gt; -45,7 +45,7 &amp;lt; at &amp;gt;&amp;lt; at &amp;gt; Display help message and exit.
 .TP
 \fB\-p\fR, \fB\-\-protection-period=\fIinterval\fR
 Set protection period for a cleaner run.  The \fIinterval\fR parameter
-is an interger value and specifies the minimum time that deleted or
+is an integer value and specifies the minimum time that deleted or
 overrode data will be preserved in the file system.  Smaller values will
 increase free space made by garbage collection.  Optionally, the
 \fIinterval\fP parameter may be suffixed by one of the following

--
Best regards,
Tiago Caxias
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Tiago Caxias</dc:creator>
    <dc:date>2012-05-02T14:44:33</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2334">
    <title>Nilfs2 and Grub2</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2334</link>
    <description>&lt;pre&gt;Hi list,

I have done some observations with the combination
grub2 and nilfs2 on the boot partition. It would
be valuable to know if anyone else has done similar
observations or if this is a {,/un}known problem.


After some harsh handling the system is rebooted
and grub2 hangs during stage 1.5-2. Once grub2 has
encountered this problem it is consistent. It will
hang on every consecutive boot.

However, if the filesystem (on a CF) is mounted by
another system there are no problems reported.
Furthermore, once the filesystem has been mounted
by another system grub2 has no problems booting it
again afterwards. There is no need to do anything
else with the fs than mounting it by another system
and then umount it again.
My preliminary analysis is:
 * Nilfs2 is left in a disturbed state, due to some
   rough handling (still unknown in detail).
 * A normal mount has no problem to recover the fs
   in such case.
 * Grub2 lacks some of the recovery features
   performed during a normal mount and will have
   problem reading files on the fs.

Currently I do not have a more exact description of
the problem. I still have to figure out exactly what
handling that triggers this state for the fs.


This is an embedded project and a previous version

is running grub legacy and ext2 without any signs of
similar problems. Grub legacy has never failed, even
with a (partly) corrupt ext2.

My own knowledge in the nilfs2/grub2 internals is
limited and it is hard to troubleshoot since I
have no recipe reproduction. However, I have observed
it on several occasions on our test systems. I am on
a tight schedule, but when time permits, I will try
to find a way to reproduce this.

Have anyone experienced similar behavior?

Brgds
/Sven

--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>Sven-Göran Bergh</dc:creator>
    <dc:date>2012-05-01T10:38:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2331">
    <title>Advanced Cloud Hosting/Server</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2331</link>
    <description>&lt;pre&gt;Dear All,

Shoud you need Web, Email, EDM, Streaming, FTP.......server or hosting space?

We have providing better and lower cost service of Cloud Hosting (Cloud Server / Hosting / CDN)

Just USD$1.99 for experience, let's come to join us and enjoy our powerful and stable cloud system.

Please kindly visit our website as following link for more details. Thank you very much.

http://www.cloudluca.com/ 

Best Regards,
The 36cloud Team





If you do not wish to further receive this event message, email "subscriber-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0&amp;lt; at &amp;gt;public.gmane.org" to unsubscribe this message or revoe 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&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>woody-3GeZWEQ5Z0yB+jHODAdFcQ&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-04-25T13:15:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2328">
    <title>Server Rental Service in HK</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2328</link>
    <description>&lt;pre&gt;Dear All,

We have our own datacenter in Hong Kong &amp;amp; provide email/application/web rental service to clients.We are APNIC member &amp;amp; provide clean IP to clients.

Dell? PowerEdge? EnterpriseRack Mount Server
-Intel(R) Xeon(R) E3-1240 Processor (3.3GHz, 8M Cache, Turbo, 4C/8T, 80W)
-8GB RAM, 2x4GB, 1333MHz, DDR-3, Dual Ranked UDIMMs
-500GB, 3.5", 6Gbps SAS x 2
-Raid 1 Mirroring Protection
-Remote KVM (iDRAC6 Enterprise)

Dell(TM) PowerEdge(TM) R410 Rack Mount Server
-Intel(R) Quad Core E5606 Xeon(R) CPU, 2.13GHz, 4M Cache, 4.86 GT/s QPI
-4GB Memory (2x2GB), 1333MHz Dual Ranked RDIMMs Fully-Buffered
-500GB 7.2K RPM SATAII 3.5" Hard Drive x 2
-iDRAC6 Enterprise or Express (Remote KVM Management)

Every Dedicated Server Hosting Solution Also Includes: 
 
Software Specification 
- CentOS / Fedora / Debian / FreeBSD / Ubuntu / Redhat Linux 
- Full root-level access 
- Data Center Facilities 
- Shared Local &amp;amp; International Bandwidth 
- 2 IP Addresses Allocation 
- Un-interruptible Power Supply (UPS) backed up by private diesel generator 
- FM200¡§based fire suppression system 
- 24x7 CRAC Air Conditioning and Humidity Control 
- 24x7 Security Control 
- 24x7 Remote Hand Service 

Pls send us email for further information.Thanks,

Boris 
boris-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0&amp;lt; at &amp;gt;public.gmane.org

If you do not wish to further receive this event message, email "borislamsv2-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;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&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>boris-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-04-22T00:42:50</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2327">
    <title>NILFS development contribution</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2327</link>
    <description>&lt;pre&gt;Hi,
I have gone through the documents of NILFS mentioned on the home page
of NILFS. I have interest in file system development and have some
background knowledge about the linux VFS layer and have also created a
sample memory based file system which resides only in the memory. In
one of the slides "Development of a New Logstructured File System for
Linux", there is a mention to involve outside developers in the
project as well. I too want to contribute in the development of nilfs
so I wanted to know where can I start from to get involved in the
project.can any one help me for  to get start please.

Thanks,
karuanakar.
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>santhosh kumars</dc:creator>
    <dc:date>2012-04-18T11:05:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2324">
    <title>Server Rental Service in Hong Kong</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2324</link>
    <description>&lt;pre&gt;Dear All,

We have our own datacenter in Hong Kong &amp;amp; provide email/application/web rental service to clients.We are APNIC member &amp;amp; provide clean IP to clients.

Dell? PowerEdge? EnterpriseRack Mount Server
-Intel(R) Xeon(R) E3-1240 Processor (3.3GHz, 8M Cache, Turbo, 4C/8T, 80W)
-8GB RAM, 2x4GB, 1333MHz, DDR-3, Dual Ranked UDIMMs
-500GB, 3.5", 6Gbps SAS x 2
-Raid 1 Mirroring Protection
-Remote KVM (iDRAC6 Enterprise)

Dell(TM) PowerEdge(TM) R410 Rack Mount Server
-Intel(R) Quad Core E5606 Xeon(R) CPU, 2.13GHz, 4M Cache, 4.86 GT/s QPI
-4GB Memory (2x2GB), 1333MHz Dual Ranked RDIMMs Fully-Buffered
-500GB 7.2K RPM SATAII 3.5" Hard Drive x 2
-iDRAC6 Enterprise or Express (Remote KVM Management)

Every Dedicated Server Hosting Solution Also Includes: 
 
Software Specification 
- CentOS / Fedora / Debian / FreeBSD / Ubuntu / Redhat Linux 
- Full root-level access 
- Data Center Facilities 
- Shared Local &amp;amp; International Bandwidth 
- 2 IP Addresses Allocation 
- Un-interruptible Power Supply (UPS) backed up by private diesel generator 
- FM200¡§based fire suppression system 
- 24x7 CRAC Air Conditioning and Humidity Control 
- 24x7 Security Control 
- 24x7 Remote Hand Service 

Pls send us email for further information.Thanks,

Boris 
boris-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0&amp;lt; at &amp;gt;public.gmane.org

If you do not wish to further receive this event message, email "borislamsv2-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;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&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>boris-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-04-17T09:45:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2316">
    <title>Our Dedicated Server Prices Help Your Bottom Line</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2316</link>
    <description>&lt;pre&gt;All Dedicated Server service included hosting to our Data Center:

Facilities:

Over 20,000ft Data Center with Control Center
Holds Certificate of ISO/IEC 27001:2005
Standard of TIA-942 Tier 3+ Facilities

FM200 and HSSD ¡V strengthens fire resistance and limits potential damage
CRAC system ¡V maintains constant temperatures and relative humidity to minimize redundancy control
Diesel Power Generator ¡V provide full power outage support for entire data centre operation with limitless diesel tank back up located in ground floor of building.
UPS ¡V offers N+1 full load configuration

Service Features:

Server is collocated in Standard 42U Industries Rack.
1000Mbps Internet Connectivity shared backbone access
IP(s) pre-allocated
Included Server Power Consumption
24x7 Technical Support (On-phone / Email)
24x7 Security Control
24x7 Network Monitoring Service
24x7 Server Status and Traffic Monitoring
Network Firewall protected

Pls send us email for further information.Thanks,

Boris 
boris-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0&amp;lt; at &amp;gt;public.gmane.org

If you do not wish to further receive this event message, email "borislamsv2-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;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&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>boris-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-04-13T12:28:09</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2315">
    <title>Server Rental Service in HK</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2315</link>
    <description>&lt;pre&gt;Dear All,

We have our own datacenter in Hong Kong &amp;amp; provide email/application/web rental service to clients.We are APNIC member &amp;amp; provide clean IP to clients.

Dell? PowerEdge? EnterpriseRack Mount Server
-Intel(R) Xeon(R) E3-1240 Processor (3.3GHz, 8M Cache, Turbo, 4C/8T, 80W)
-8GB RAM, 2x4GB, 1333MHz, DDR-3, Dual Ranked UDIMMs
-500GB, 3.5", 6Gbps SAS x 2
-Raid 1 Mirroring Protection
-Remote KVM (iDRAC6 Enterprise)

Dell(TM) PowerEdge(TM) R410 Rack Mount Server
-Intel(R) Quad Core E5606 Xeon(R) CPU, 2.13GHz, 4M Cache, 4.86 GT/s QPI
-4GB Memory (2x2GB), 1333MHz Dual Ranked RDIMMs Fully-Buffered
-500GB 7.2K RPM SATAII 3.5" Hard Drive x 2
-iDRAC6 Enterprise or Express (Remote KVM Management)

Every Dedicated Server Hosting Solution Also Includes: 
 
Software Specification 
- CentOS / Fedora / Debian / FreeBSD / Ubuntu / Redhat Linux 
- Full root-level access 
- Data Center Facilities 
- Shared Local &amp;amp; International Bandwidth 
- 2 IP Addresses Allocation 
- Un-interruptible Power Supply (UPS) backed up by private diesel generator 
- FM200¡§based fire suppression system 
- 24x7 CRAC Air Conditioning and Humidity Control 
- 24x7 Security Control 
- 24x7 Remote Hand Service 

Pls send us email for further information.Thanks,

Boris 
boris-3GeZWEQ5Z0yB+jHODAdFcQ&amp;lt; at &amp;gt;public.gmane.org

If you do not wish to further receive this event message, email "borislamsv2-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;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&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>boris-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-04-12T08:41:26</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2314">
    <title>Server Rental Service in Hong Kong</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2314</link>
    <description>&lt;pre&gt;Dear All,

We have our own datacenter in Hong Kong &amp;amp; provide email/application/web rental service to clients.We are APNIC member &amp;amp; provide clean IP to clients.

Dell? PowerEdge? EnterpriseRack Mount Server
-Intel(R) Xeon(R) E3-1240 Processor (3.3GHz, 8M Cache, Turbo, 4C/8T, 80W)
-8GB RAM, 2x4GB, 1333MHz, DDR-3, Dual Ranked UDIMMs
-500GB, 3.5", 6Gbps SAS x 2
-Raid 1 Mirroring Protection
-Remote KVM (iDRAC6 Enterprise)

Dell(TM) PowerEdge(TM) R410 Rack Mount Server
-Intel(R) Quad Core E5606 Xeon(R) CPU, 2.13GHz, 4M Cache, 4.86 GT/s QPI
-4GB Memory (2x2GB), 1333MHz Dual Ranked RDIMMs Fully-Buffered
-500GB 7.2K RPM SATAII 3.5" Hard Drive x 2
-iDRAC6 Enterprise or Express (Remote KVM Management)

Every Dedicated Server Hosting Solution Also Includes: 
 
Software Specification 
- CentOS / Fedora / Debian / FreeBSD / Ubuntu / Redhat Linux 
- Full root-level access 
- Data Center Facilities 
- Shared Local &amp;amp; International Bandwidth 
- 2 IP Addresses Allocation 
- Un-interruptible Power Supply (UPS) backed up by private diesel generator 
- FM200¡§based fire suppression system 
- 24x7 CRAC Air Conditioning and Humidity Control 
- 24x7 Security Control 
- 24x7 Remote Hand Service 

Pls send us email for further information.Thanks,

Boris 
boris-3GeZWEQ5Z0yB+jHODAdFcQ&amp;lt; at &amp;gt;public.gmane.org

If you do not wish to further receive this event message, email "borislamsv2-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;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&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>boris-3GeZWEQ5Z0yB+jHODAdFcQ&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-04-05T14:14:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2313">
    <title>Cloud Hosting and Cloud Server</title>
    <link>http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2313</link>
    <description>&lt;pre&gt;Dear All,

We are one of the top Cloud Solution provider base in Hong Kong, with over 10+ years experience,
we providing better than good and lower cost service of CLoud Hosting (Cloud Server / Hosting / CDN)

Starting at $1.99, let's come to experience and enjoy our powerful cloud system.

Thanks for your time and appreciated to look arround our website.

http://www.dedicatedserver.com.hk/ 

Best Regards,
The 36cloud Team





If you do not wish to further receive this event message, email "subscriber-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0&amp;lt; at &amp;gt;public.gmane.org" to unsubscribe this message or revoe your email from the list.

Any questions, please feel free to contact our CS at cs-BJI9bKMaVxBBDgjK7y7TUQ&amp;lt; at &amp;gt;public.gmane.org . 

We are highly appreciated your attention, and just come to experience our powerful cloud server service.

Best Regards,
The 36cloud CS team
Email: cs-BJI9bKMaVxBBDgjK7y7TUQ&amp;lt; at &amp;gt;public.gmane.org 
Website: http://www.36cloud.com
**************************************************************************


If you do not wish to further receive this event message, email "subscriber-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0&amp;lt; at &amp;gt;public.gmane.org" to unsubscribe this message or revoe 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&amp;lt; at &amp;gt;public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

&lt;/pre&gt;</description>
    <dc:creator>woody-JYBpPTDdvJEqwVFMiTZqHLZc9IWuHzk0&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2012-04-02T13:07:39</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.file-systems.nilfs.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.file-systems.nilfs.user</link>
  </textinput>
</rdf:RDF>

