http://blog.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://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2926 <pre>From: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; Subject: [PATCH v5 2/2] nilfs2: use atomic_long_t type for inodes_count and blocks_count fields in nilfs_root struct The cp_inodes_count and cp_blocks_count are represented as __le64 type in on-disk structure (struct nilfs_checkpoint). But analogous fields in in-core structure (struct nilfs_root) are represented by atomic_t type. This patch replaces atomic_t on atomic_long_t type in representation of inodes_count and blocks_count fields in struct nilfs_root. Signed-off-by: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; CC: Ryusuke Konishi &lt;konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg&lt; at &gt;public.gmane.org&gt; --- fs/nilfs2/ifile.c | 2 +- fs/nilfs2/inode.c | 8 ++++---- fs/nilfs2/segment.c | 4 ++-- fs/nilfs2/super.c | 8 +++++--- fs/nilfs2/the_nilfs.c | 4 ++-- fs/nilfs2/the_nilfs.h | 4 ++-- 6 files changed, 16 insertions(+), 14 deletions(-) diff --git a/fs/nilfs2/ifile.c b/fs/nilfs2/ifile.c</pre> Vyacheslav Dubeyko 2013-05-24T13:32:52 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2925 <pre>From: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; Subject: [PATCH v5 1/2] nilfs2: implement calculation of free inodes count Currently, NILFS2 returns 0 as free inodes count (f_ffree) and current used inodes count as total file nodes in file system (f_files): df -i Filesystem Inodes IUsed IFree IUse% Mounted on /dev/loop0 2 2 0 100% /mnt/nilfs2 This patch implements real calculation of free inodes count. First of all, it is calculated total file nodes in file system as (desc_blocks_count * groups_per_desc_block * entries_per_group). Then, it is calculated free inodes count as difference the total file nodes and used inodes count. As a result, we have such output for NILFS2: df -i Filesystem Inodes IUsed IFree IUse% Mounted on /dev/loop0 4194304 2114701 2079603 51% /mnt/nilfs2 Reported-by: Clemens Eisserer &lt;linuxhippy-Re5JQEeQqe8AvxtiuMwx3w&lt; at &gt;public.gmane.org&gt; Signed-off-by: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane</pre> Vyacheslav Dubeyko 2013-05-24T13:32:35 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2920 <pre>Greetings! It pains me to report that my /home filesystem broke down today. My system is running Arch Linux 64-bit. The filesystem resides on a Crucial M4 256 GB SSD, on top of a LVM2 volume. The drive and filesystem are both around six months old. Partition table and error log excerpts are at the bottom of this e-mail. Full logs are available upon request. I am providing this information as a bug report. I have no reason to suspect the hardware but I cannot exclude it either. If you (the developers) are interested in troubleshooting this for prosperity, I can be your hands and run whatever tools are required. If not, I'll reformat the filesystem, restore the data from backup and forget that this happened. In case the formatting gets mangled, this e-mail is also available at What happened today, in chronological order: ~18:00 ====== I am troubleshooting some issues that turn out to be caused by a wrongly configured system clock. The RTC (hardware clock) is set to local time (UTC+2) but the OS i</pre> Anton Eliasson 2013-05-22T20:33:26 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2905 <pre>Hi Ryusuke, This is second version of the patch. v1-&gt;v2 * Change __statfs_word on u64 type. * Rename nilfs_count_free_inodes() into nilfs_ifile_count_free_inodes() method. * Introduce auxiliary functions: nilfs_palloc_count_max_entries(), nilfs_palloc_count_desc_blocks(), nilfs_palloc_mdt_file_can_grow(). * Rework processing of returned error from nilfs_ifile_count_free_inodes() in nilfs_statfs(). With the best regards, Vyacheslav Dubeyko. --- From: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; Subject: [PATCH v2] nilfs2: implement calculation of free inodes count Currently, NILFS2 returns 0 as free inodes count (f_ffree) and current used inodes count as total file nodes in file system (f_files): df -i Filesystem Inodes IUsed IFree IUse% Mounted on /dev/loop0 2 2 0 100% /mnt/nilfs2 This patch implements real calculation of free inodes count. First of all, it is calculated total file nodes in file system as (desc_blocks_count * groups_per_desc_block</pre> Vyacheslav Dubeyko 2013-05-13T11:54:51 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2903 <pre> Entschuldigungen für kommen in Ihre Privatsphäre! Ich bin Rechtsanwalt Werner Erich Zeller; Ich habe einen meiner einflussreichen und wohlhabenden Kunden zum Tode; und er hatte eine sehr geheime und private Investitionen von €15,000,000.00 bei einer privaten Bank in Großbritannien hier zu Lebzeiten. Diese Investition wurde ohne einen deklarierten nächsten Angehörigen und begünstigte. Jetzt brauche ich Sie arbeiten mit mir als mein Partner zu erholen und zu je 50 % Aktienfonds. Alle Dokumente werden rechtlich beantragt und beschafft, und in 5 Werktage, wird diese Transaktion auftreten. Aber ich brauche einen ernsten, treuen und glaubwürdigen Partner. Bitte senden Sie mir eine vertrauliche Antwort, wenn Sie denken, Sie vertraut werden können und sind von den Qualitäten! Ich warte auf Ihre schnelle Antwort. Werner Erich Zeller (Rechtsanwalt) Rufen Sie + 44-702-409-0820 (Office) -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to majordomo-u79uwXL2</pre> John P. Goldman 2013-05-08T08:46:28 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2893 <pre>Hi Vyacheslav, Here I post the bug fix of the problem that Anthony Doggett reported and you originally proposed a bug fix with the patch titled "nilfs2: fix issue with broken bmap for the case of block size lesser than 4 KB". I tested this patch against the mainline and stable trees, and so far it works fine (the issue is fixed without any side effect). If you meet an issue on this patch, or have a question, please let me know. I appreciate very much that you are always making effort to solve problems of NILFS users. Thanks, Ryusuke Konishi -- From: Ryusuke Konishi &lt;konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg&lt; at &gt;public.gmane.org&gt; Subject: [PATCH] nilfs2: fix issue of nilfs_set_page_dirty for page at EOF boundary DESCRIPTION: There are use-cases when NILFS2 file system (formatted with block size lesser than 4 KB) can be remounted in RO mode because of encountering of "broken bmap" issue. The issue was reported by Anthony Doggett &lt;Anthony2486-fDpYTK8McCxDP812hmKXO1pr/1R2p/CL&lt; at &gt;public.gmane.org&gt;: "The machine I'v</pre> Ryusuke Konishi 2013-05-01T07:39:30 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2879 <pre>Hi again, I was able to trace the performance issues down to the "slub_debug" kernel option which is set in fedora test builds. With this option disabled performance is not great, but not that bad either (~110mb/s on an SSD which usually does 400mb/s sequential). Thanks a lot for nilfs, hopefully it will reduce my suffering after accidential command line desasters ;) Thanks, Clemens -- 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> Clemens Eisserer 2013-04-24T14:22:48 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2878 <pre>Hi. I am in the process of migrating to nilfs2 for my root-filesystem running Fedora-19-alpha. Basically the system works quite fine, except: 1. RPM checks for free inodes prior installing a package, which doesn't make any sence of course. I can pass "--ignoresize" to RPM which disables those checks, however, I haven't found any way to disable it when using the "yum" package manager. Is there any way to make nilfs2 report a large number of unused inodes instead of "0"? 2. Write-operations are very slow (a few mb/s) and a lot of time is spent inside: - segctord - the application performing the filesystem operations. I've recorded a system-wide profile of extracting a tar archive as well as a larger delete operation (rm): https://plus.google.com/photos/118350688762629274389/albums/5870410083987119137?authkey=CPu0iK2TiOWsoQE Any idea what could be going wrong here? Thank you in advance, Clemens PS: I am using nilfs-utils-2.1.4-3.fc19.x86_64 and linux 3.9.0-0.rc6.git2.3.fc19.x86_64. the root-filesystem is</pre> Clemens Eisserer 2013-04-24T13:53:24 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2861 <pre>Dear NILFS team, Let me thank you sincerely for fantastic and very special file system. Until now I've been using it successfully for years without any issues except for minor inconvenience from slow `nilfs_cleanerd`. I'd like to share the details of the incident when recently I experienced data corruption on NILFS2 partition followed by unfortunate adding of unreliable "SAMSUNG HD204UI" HDD to underlying "mdadm" array. The notorious HDD [1][2] occasionally corrupts data on write so later read returns wrong data. There is no way to avoid such corruption in first place. Detection is also difficult because as you may know in Linux there is no block-level integrity checking yet. However NILFS2 suffers the most from that particular type of corruption because `nilfs_cleanerd` moves unmodified data around and therefore amplifies the damage. First I noticed corruption on some archives that were OK some weeks ago and didn't change since (according to last modification date). As time passed more damage was found</pre> Dmitry Smirnov 2013-04-05T04:45:16 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2850 <pre> I am Barrister Werner Erich Zeller; I need your sincere partnership in transferring the sum of 15,000,000.00 EUR The details await you as you reply! please! Call +44 702 409 0820 (office) </pre> Michele Roca 2013-03-27T08:10:09 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2848 <pre>Hi, I think that NILFS2 very needs in good debug infrastructure and tracepoints adding. So, this first patch is my vision of necessary declarations and methods for debug output. This patch is only for discussion because I am working on patch set with debug output for all NILFS2 modules. Feel free to suggest any ideas and make remarks about debug output infrastructure in NILFS2. With the best regards, Vyacheslav Dubeyko. --- From: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; Subject: [PATCH] nilfs2: add necessary declarations and methods for debug output infrastructure This patch adds necessary declarations and methods for debug output infrastructure. Signed-off-by: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; --- fs/nilfs2/nilfs.h | 77 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 77 insertions(+) diff --git a/fs/nilfs2/nilfs.h b/fs/nilfs2/nilfs.h index 9bc72de..4102667 100644 --- a/fs/nilfs2/nilfs.h +++ b/fs/nilfs2/nilfs.h &lt; at &gt;&lt; at &gt; -32</pre> Vyacheslav Dubeyko 2013-03-26T10:09:33 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2847 <pre> </pre> e639-aFiDPoud36g< at >public.gmane.org 2013-03-26T07:27:54 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2846 <pre> </pre> e639-aFiDPoud36g< at >public.gmane.org 2013-03-26T07:25:41 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2845 <pre>From: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; Subject: [PATCH v3] nilfs-utils: mkfs.nilfs2 should check presence of NILFS2 volume on device The mkfs.nilfs2 utility should check presence of existing file system or partition table on device and to warn a user about possibility to destroy data by mkfs activity. This patch uses libblkid library for detection of presence of file system or partition table on opened device. If libblkid detects any known signature then mkfs.nilfs2 informs a user about potential danger to destroy existing file system or partition table. The execution of mkfs.nilfs2 stops with offering to make decision about continuation or abortion of operation. Moreover, this patch adds "-f" option that gives opportunity to force overwrite when an existing file system is detected on the device. By default, mkfs.nilfs2 will not write to the device if it suspects that there is a file system on the device already. The man page of mkfs.nilfs2 was modified by description of "</pre> Vyacheslav Dubeyko 2013-03-25T11:47:21 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2837 <pre>From: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; Subject: [PATCH v2] nilfs-utils: mkfs.nilfs2 should check presence of NILFS2 volume on device The mkfs.nilfs2 utility should check presence of NILFS2 volume on device and to warn a user about possibility to destroy data by mkfs activity. This patch tries to read and to validate checksums of primary and secondary superblocks on opened device. If this operation ends successfully then mkfs.nilfs2 informs a user about potential danger to destroy existing NILFS2 volume. The execution of mkfs.nilfs2 stops with offering to make decision about continuation or abortion of operation. Moreover, this patch adds "-f" option that gives opportunity to force overwrite when an existing NILFS2 filesystem is detected on the device. By default, mkfs.nilfs2 will not write to the device if it suspects that there is a filesystem on the device already. The man page of mkfs.nilfs2 was modified by description of "-f" option. Reported-by: Hendrik Levsen &lt;hendr</pre> Vyacheslav Dubeyko 2013-03-24T11:58:57 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2835 <pre>From: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; Subject: [PATCH] nilfs-utils: mkfs.nilfs2 should check presence of NILFS2 volume on device The mkfs.nilfs2 utility should check presence of NILFS2 volume on device and to warn a user about possibility to destroy data by mkfs activity. This patch tries to read and to validate checksums of primary and secondary superblocks on opened device. If this operation ends successfully then mkfs.nilfs2 informs a user about potential danger to destroy existing NILFS2 volume. The execution of mkfs.nilfs2 stops with offering to make decision about continuation or abortion of operation. However, if a user runs mkfs.nilfs2 with "-q" option then checking of NILFS2 volume is skipped. Reported-by: Hendrik Levsen &lt;hendrik-j5CO6tLloWodnm+yROfE0A&lt; at &gt;public.gmane.org&gt; Signed-off-by: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; Tested-by: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; --- sbin/mkfs/Makefile.am | 3 ++</pre> Vyacheslav Dubeyko 2013-03-23T11:45:22 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2834 <pre> </pre> WERNER ERICH ZELLER 2013-03-21T23:57:10 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2832 <pre>Hi, I may have issued an mkfs command onto an already existing, healthy NILFS volume. This is nothing that can be undone, can it? Regards Hendrik -- 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> Hendrik Levsen 2013-03-22T16:42:56 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2817 <pre>Hello! First of all, thank you for the nilfs2. I have been using this filesystem for few years on different types of storage ranging from small SSDs to huge 10+TB volumes on big arrays with no a single problem but now I am stuck with a broken volume. The long story short. I have a laptop which runs vanilla linux-3.8.2 with nilfs on root partition (and nilfs-utils-2.1.4, if that matters; the volume has been created with 2.0.*-series of nilfs-utils with default options). Yesterday I noticed it doesn't switch its display off (probably because of some failed io) and continously displays a screensaver but I didn't touch it. Today I touched it to see that it deadly hung. I had to power cycle the laptop and since then the kernel cannot mount rootfs with: NILFS: Invalid checkpoint (checkpoint number=5439464) NILFS: error loading last checkpoint (checkpoint number=5439464) I booted from a USB flash and inspected S.M.A.R.T attributes of the HDD. It looks absolutely healthy. Of remarkable events, couple of months</pre> Alexander Bezrukov 2013-03-15T02:40:19 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2812 <pre>Hi Thanks for nilfs:) I have been trying it out again recently, this time using 1kB blocks for the partitions containing often-appended files like those in $HOME and /var. Unfortunately the 1kB partitions keep dying; I detail the one of the common failures that I've managed to cut down below. I started using nilfs with the default block/segment size, but was surprised how many blocks get appended by operations like "echo something &gt;&gt; something.txt". Decreasing the block size from 4kB to 1kB reduced the amount of disk space required to house partitions containing $HOME and /var/log by about 60%. The machine I've been trialling nilfs on is running Debian Testing, Linux version 3.2.0-4-686-pae (debian-kernel-0aAXYlwwYIJuHlm7Suoebg&lt; at &gt;public.gmane.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.2.35-2), but I've also reproduced it (identically) with Debian Unstable amd64 and Debian Experimental (using the 3.8-trunk kernel). The problematic partitions were formatted with "mkfs.nilfs2 -b 1024 -B 819</pre> Anthony Doggett 2013-03-13T07:14:53 http://comments.gmane.org/gmane.comp.file-systems.nilfs.user/2808 <pre>From: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; Subject: [PATCH] fix warning in fs/nilfs2/btree.c: In function ‘nilfs_btree_convert_and_insert’ This patch fixes the warning in fs/nilfs2/btree.c: In function ‘nilfs_btree_convert_and_insert’: (1) include/asm/bitops.h:321:8: warning: ‘bh’ may be used uninitialized in this function [-Wuninitialized] Signed-off-by: Vyacheslav Dubeyko &lt;slava-yeENwD64cLxBDgjK7y7TUQ&lt; at &gt;public.gmane.org&gt; --- fs/nilfs2/btree.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/fs/nilfs2/btree.c b/fs/nilfs2/btree.c index b2e3ff3..734ece9 100644 --- a/fs/nilfs2/btree.c +++ b/fs/nilfs2/btree.c &lt; at &gt;&lt; at &gt; -1767,7 +1767,7 &lt; at &gt;&lt; at &gt; int nilfs_btree_convert_and_insert(struct nilfs_bmap *btree, __u64 key, __u64 ptr, const __u64 *keys, const __u64 *ptrs, int n) { -struct buffer_head *bh; +struct buffer_head *bh = NULL; union nilfs_bmap_ptr_req dreq, nreq, *di, *ni; struct nilfs_bmap_stats stats; int ret; </pre> Vyacheslav Dubeyko 2013-03-03T15:26:56 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.file-systems.nilfs.user