This makes use of iget5_locked to allocate or get inode for metadata
files to stop using own inode allocator.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/cpfile.c| 49 +
fs/nilfs2/cpfile.h|4 +-
fs/nilfs2/dat.c
This finally removes own inode allocator and destructor functions for
metadata files. Several routines, nilfs_mdt_new(),
nilfs_mdt_new_common(), nilfs_mdt_clear(), nilfs_mdt_destroy(), and
nilfs_alloc_inode_common() will be gone.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
respectively).
Before DAT changes block number in an entry block, it makes a copy and
redirect access to the buffer so that address conversion function
(i.e. nilfs_dat_translate) refers to the old address saved in the
copy.
This patch gives requisites for such redirection.
Signed-off-by: Ryusuke Konishi
the
unification of sb.
To prepare for the issue, this uses i_op-permission to deny write
access to inodes in snapshots.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/inode.c | 11 +++
fs/nilfs2/namei.c |1 +
fs/nilfs2/nilfs.h |4 +---
3 files changed, 13
number.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/export.h | 17 ++
fs/nilfs2/namei.c| 137 --
fs/nilfs2/nilfs.h|3 -
fs/nilfs2/super.c| 52 +-
include/linux
-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/btnode.c | 17 +---
fs/nilfs2/mdt.c| 104 ++--
fs/nilfs2/mdt.h| 14 +++
fs/nilfs2/page.c | 25
fs/nilfs2/page.h |4 ++
5 files changed, 145
library is key to propagate nilfs2 user land
implementations and which library is good to be LGPLed, I think.
Reasonable. At least, I agree with the licence migration. Let's
consider how to avoid the minor license issue above.
Thanks,
Ryusuke Konishi
--
To unsubscribe from this list: send the line
warn_unused_result
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
lib/sb.c | 15 +++
sbin/nilfs-tune/nilfs-tune.c | 10 +++---
2 files changed, 18 insertions(+), 7 deletions(-)
diff --git a/lib/sb.c b/lib/sb.c
index 293cd6f..d93504c 100644
��, declared with
attribute warn_unused_result
This kills these warnings.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
bin/chcp.c|3 ++-
bin/dumpseg.c |3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/bin/chcp.c b/bin/chcp.c
index deb9a2b..a66e437
__releases() and __acquires() as below.
static void nilfs_segctor_kill_thread(struct nilfs_sc_info *sci)
+ __releases(sci-sc_state_lock)
+ __acquires(sci-sc_state_lock)
{
You can find this style of examples in other sites in the kernel.
Thanks,
Ryusuke Konishi
--
To unsubscribe from
this comment should be included in the changelog. It's
a common manner in kernel, and the comment adds a note on the sparse
tool. Describing it in the implementation seems verbose.
Ryusuke Konishi
static void nilfs_segctor_kill_thread(struct nilfs_sc_info *sci)
+ __acquires(sci-sc_state_lock
it for business use. NILFS2 is
still marked experimental in kernel as with BTRFS.
Thanks,
Ryusuke Konishi
--
To unsubscribe from this list: send the line unsubscribe linux-nilfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
.
sparse doesn't detect the context and warn unexpected unlock.
__acquires/__releases pretend to lock/unlock the sc_state_lock for sparse.
Signed-off-by: Jiro SEKIBA j...@unicus.jp
Applied.
Thanks for your cooperation.
Ryusuke Konishi
---
fs/nilfs2/segment.c |2 ++
1 files changed, 2
On Thu, 14 Oct 2010 07:55:44 -0500, Dwight Schauer wrote:
On Thu, Oct 14, 2010 at 7:25 AM, Jérôme Poulin jeromepou...@gmail.com wrote:
On my side, it is on my laptop /home partition for a bit more than a year...
On Thu, Oct 14, 2010 at 1:50 AM, Ryusuke Konishi
konishi.ryus...@lab.ntt.co.jp
NILFS2 filesystem section of the MAINTAINERS file lacks an entry of
scm tree. This adds it.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
MAINTAINERS |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index a92c994..c68e816
Will correct the following checkpatch error:
ERROR: trailing whitespace
#494: FILE: page.c:494:
+ $
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/page.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/nilfs2/page.c b/fs/nilfs2/page.c
nilfs_page_get_nth_block() function used in nilfs_mdt_freeze_buffer()
always returns a valid buffer head, so its validity check can be
removed.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/mdt.c | 26 --
1 files changed, 12 insertions
and NOATIME to be set on non-regular file,
non-directories.
This introduces a flags masking function like those of extN and uses
it during inode creation.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/inode.c |7 ++-
fs/nilfs2/nilfs.h | 17 +
2 files
, and the fourth one adds these ioctls.
Ryusuke Konishi
--
Ryusuke Konishi (4):
nilfs2: use common file attribute macros
nilfs2: mark S_NOATIME on inodes only if NOATIME attribute is set
nilfs2: tighten restrictions on inode flags
nilfs2: implement FS_IOC_GETFLAGS/SETFLAGS
Replaces uses of own inode flags (i.e. NILFS_SECRM_FL, NILFS_UNRM_FL,
NILFS_COMPR_FL, and so forth) with common inode flags, and removes the
own flag declarations.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/dir.c |3 ---
fs/nilfs2/inode.c
..
http://www.spinics.net/lists/linux-nilfs/msg00595.html
thanks
The warning message is already taken away from the latest tree on
nilfs-utils.git, but we haven't yet made a release of it.
Okay, I will do a 2.0.21 later this week.
Thanks,
Ryusuke Konishi
--
To unsubscribe from this list: send
This patch fixes a crash issue recently reported by Wakko Warner.
I will send this upstream and to stable after a while.
Ryusuke Konishi
--
From: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
nilfs2: fix crash after one superblock became unavailable
Fixes the following kernel oops
be suppressed if we don't rewrite
carefully. It seems like such change doesn't clarify things after
all.
This patch, instead, relieves the confusion just by adding block size
information to those warnings.
Ryusuke Konishi
--
From: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
nilfs2: append blocksize
Linus,
please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git for-linus
to grab the following bugfix for a reported kernel oops.
Thanks,
Ryusuke Konishi
--
The following changes since commit 1bae4ce27c9c90344f23c65ea6966c50ffeae2f5:
Linux 2.6.38-rc2 (2011-01
The current FS_IOC_GETFLAGS/SETFLAGS/GETVERSION will fail if
application is 32 bit and kernel is 64 bit.
This issue is avoidable by adding compat_ioctl method.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/dir.c |2 +-
fs/nilfs2/file.c |2 +-
fs/nilfs2
is always set on sb.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/inode.c |2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/fs/nilfs2/inode.c b/fs/nilfs2/inode.c
index b97bcfc..2db4e92 100644
--- a/fs/nilfs2/inode.c
+++ b/fs/nilfs2/inode.c
@@ -365,9
Replaces uses of own inode flags (i.e. NILFS_SECRM_FL, NILFS_UNRM_FL,
NILFS_COMPR_FL, and so forth) with common inode flags, and removes the
own flag declarations.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/dir.c |3 ---
fs/nilfs2/inode.c
i_generation, which allows users to list the file's generation number
with lsattr -v.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/ioctl.c | 70 +
1 files changed, 70 insertions(+), 0 deletions(-)
diff --git a/fs/nilfs2
is
32 bit but kernel is 64 bit.
* rebased to v2.6.38-rc3
Ryusuke Konishi
--
Ryusuke Konishi (5):
nilfs2: use common file attribute macros
nilfs2: mark S_NOATIME on inodes only if NOATIME attribute is set
nilfs2: tighten restrictions on inode flags
nilfs2: implement
the architecture cannot
even support 64k blocks. This will cut the corner.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/ioctl.c |1 +
include/linux/nilfs2_fs.h |4
2 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/fs/nilfs2/ioctl.c b/fs
the tar ball.
git://timebrowse.git.sourceforge.net/gitroot/timebrowse/timebrowse
It works fine, but looks git tag is missing. It's helpful to mark
the commit on which you made a release.
$ git tag -a v0.1
Cheers,
Ryusuke Konishi
--
To unsubscribe from this list: send the line unsubscribe
Signed-off-by: Ryusuke Konishi ryus...@osrg.net
---
nautilus/TimeBrowse.py |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/nautilus/TimeBrowse.py b/nautilus/TimeBrowse.py
index fd8c478..ad59b35 100644
--- a/nautilus/TimeBrowse.py
+++ b/nautilus/TimeBrowse.py
@@ -1,4 +1,4
Renames nilfs2_ss.conf to nilfs_ss.conf in the README file.
Signed-off-by: Ryusuke Konishi ryus...@osrg.net
---
nilfs2_ss_manager/README |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/nilfs2_ss_manager/README b/nilfs2_ss_manager/README
index 6bbacbe..8f5b798 100644
Signed-off-by: Ryusuke Konishi ryus...@osrg.net
---
.gitignore | 30 ++
1 files changed, 30 insertions(+), 0 deletions(-)
create mode 100644 .gitignore
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 000..44df3a7
--- /dev/null
+++ b/.gitignore
The error messages printed when failed to load the config file are
confusing. This makes it better.
Signed-off-by: Ryusuke Konishi ryus...@osrg.net
---
nilfs2_ss_manager/nilfs2_ss_manager | 39 ++
1 files changed, 30 insertions(+), 9 deletions(-)
diff --git
,
Ryusuke Konishi
--
To unsubscribe from this list: send the line unsubscribe linux-nilfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, 8 Feb 2011 21:32:37 +0100, Philippe CHATAIGNON wrote:
Le Tue, 08 Feb 2011 20:42:30 +0900 (JST),
Ryusuke Konishi ryus...@osrg.net a écrit :
Hi,
Thank you for the detail report! It's really helpful.
I understood the zero link count inode was causing a chain reaction
the
checkpoint automatically.
You can delete cp-68 by rmcp command without incident since the
filesystem itself is sanity.
In addition, cp-68 will be removed by GC if you will release the
snapshot cp-67.
Thanks,
Ryusuke Konishi
Running Linux 2.6.38-rc4 with nilfs-utils-2.0.21 right now
Hi,
On Thu, 10 Feb 2011 23:32:01 +0100, Philippe CHATAIGNON wrote:
Le Thu, 10 Feb 2011 14:01:05 +0900 (JST),
Ryusuke Konishi ryus...@osrg.net a écrit :
O.K. so, it seems like something happened at the checkpoint 15731
according to your information.
One thing wired is that the timestamp
Hi,
On Fri, 18 Feb 2011 20:57:39 +0100, Philippe CHATAIGNON wrote:
Le Fri, 18 Feb 2011 16:21:45 +0900 (JST),
Ryusuke Konishi ryus...@osrg.net a écrit :
Thank you for the cooperation.
Yeah, this file is exactly the file that overrode
f5_20110125_202053.ts(0).Xcl at cp15731.
I don't
This fixes the issue that inodes count will not add up after removal
of raw inodes fails. Hence, this prevents possible under flow of the
inodes count.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/inode.c |6 --
1 files changed, 4 insertions(+), 2 deletions
it.
Regards,
Ryusuke Konishi
--
To unsubscribe from this list: send the line unsubscribe linux-nilfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
and namespace into
snapshot without copying or moving blocks.
nilfs_cleanerd (NILFS GC) moves blocks per segment not per file, so
pinning files would be achieved by skipping reclamation of segments
recording the pinned files.
Thanks,
Ryusuke Konishi
--
dexen deVries
[[[↓][→]]]
how does a C
block count support.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
bin/lscp.c | 28 +---
man/lscp.1 | 12
2 files changed, 33 insertions(+), 7 deletions(-)
diff --git a/bin/lscp.c b/bin/lscp.c
index 642ed69..df9a0af 100644
--- a/bin/lscp.c
The number of used blocks by DAT file, cpfile, and sufile changes
independently of those of checkpoints. So, we stop including the
block count of those meta data files in block count of a checkpoint.
Note that the block count of ifile is still included in the block
count.
Signed-off-by: Ryusuke
.
thanks
regards,
Arrh, that sounds so bad. Ok, I'll look into the problem ASAP.
Ryusuke Konishi
It this somewhat new behavior or regression?
thanks,
regards
--
Jiro SEKIBA j...@unicus.jp
--
To unsubscribe from this list: send the line unsubscribe linux-nilfs in
the body
On Mon, 28 Feb 2011 11:21:46 +0900 (JST), Ryusuke Konishi wrote:
On Mon, 28 Feb 2011 10:58:36 +0900, Jiro SEKIBA wrote:
At Mon, 28 Feb 2011 10:33:24 +0900,
Jiro SEKIBA wrote:
Hi,
I found that none of the checpoints are flagged 'i'.
It looks like it happens after 2.6.37
in a future release.
Moreover, length of the lscp output lines will exceed 80 characters
and the output gets unfit for general terminals after applying this
patch. I think it needs to be modified in some way.
Thanks,
Ryusuke Konishi
---
bin/lscp.c | 29 -
man/lscp.1
:)
Thanks,
Ryusuke Konishi
Regards,
--
dexen deVries
[[[↓][→]]]
47. As Will Rogers would have said, There is no such thing as a free
variable.
(Alan Perlis, `Epigrams on Programming')
--
To unsubscribe from this list: send the line unsubscribe linux-nilfs in
the body of a message
(for instance,
NILFS_OPEN_ALLOW_SUBDIRS) which changes the meaning of the directory
argument slightly so that the mount point to which the given directory
belongs is selected.
Any thoughts?
Thanks,
Ryusuke Konishi
--
To unsubscribe from this list: send the line unsubscribe linux-nilfs in
the body
2011/3/4 Ryusuke Konishi ryus...@osrg.net:
In the new directory semantics, we needs to decide if a given
directory argument belongs to a mount point in the mtab entries.
This matching check needs to know whether the given directory crosses
over a filesystem boundary starting from each mount
On Fri, 04 Mar 2011 19:38:57 +0900 (JST), Ryusuke Konishi wrote:
Hi,
On Fri, 04 Mar 2011 16:56:18 +0900, Jiro SEKIBA wrote:
Hi,
At Sun, 27 Feb 2011 02:13:51 +0900,
Ryusuke Konishi wrote:
This records the number of used blocks per checkpoint in each
checkpoint entry of cpfile
deletions(-)
Thanks.
I applied the patch with a minor amendment.
Ryusuke Konishi
diff --git a/sbin/cleanerd/cleanerd.c b/sbin/cleanerd/cleanerd.c
index 1f03cfb..3d58916 100644
--- a/sbin/cleanerd/cleanerd.c
+++ b/sbin/cleanerd/cleanerd.c
@@ -1343,6 +1343,7 @@ static int
be better.
Also, looks like the device line does not have to be commented out ;)
Thanks,
Ryusuke Konishi
--
To unsubscribe from this list: send the line unsubscribe linux-nilfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Moves s_next_generation counter and a spinlock protecting it to nilfs
object from nilfs_sb_info structure.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/inode.c |8
fs/nilfs2/sb.h|4
fs/nilfs2/super.c | 11 ---
fs
Moves s_inode_lock spinlock and s_dirty_files list to nilfs object
from nilfs_sb_info structure.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/inode.c | 30 +-
fs/nilfs2/sb.h|3 --
fs/nilfs2/segment.c | 80
of filesystem at each instant of
time via lscp command.
Also, there are a cleanup series simplifying hierarchy of on-memory
structures and a few small fixes.
Thanks!
Ryusuke Konishi
--
The following changes since commit a5abba989deceb731047425812d268daf7536575:
Linux 2.6.38-rc8 (2011-03-07 21:09
lock may be applicable against directories
though I haven't tried yet. If so, we can simply use the filesystem
root directory for both purposes.
IMHO, the .nilfs file should be displaced sooner or later.
Thanks,
Ryusuke Konishi
--
To unsubscribe from this list: send the line unsubscribe linux
not permitted
This could be another work around though I don't prefer it.
Thanks,
Ryusuke Konishi
--
From: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
nilfs-utils: use root directory instead of .nilfs
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
include/nilfs.h |1
intentionally do so.
I guess the corruption problem is caused by some sort of
difficult-to-find bug at this time.
Thanks,
Ryusuke Konishi
--
To unsubscribe from this list: send the line unsubscribe linux-nilfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
This seris stops using the .nilfs file and makes it eliminable.
The first patch introduces posix semaphore for inter process locking
of nilfs-utils processes, and the second patch issues ioctl via root
directory instead of using .nilfs file.
--
To unsubscribe from this list: send the line
From: Ryusuke Konishi ryus...@osrg.net
This uses posix named semaphores instead of advisory lock of fcntl to
implement mutex between nilfs tools and the cleaner daemon. With this
change, the .nilfs file will be no longer required for the locking
purpose.
Signed-off-by: Ryusuke Konishi ryus
This issues NILFS API ioctls to for root directory of filesystem
instead of the .nilfs file.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
Cc: dexen deVries dexen.devr...@gmail.com
Cc: Reinoud Zandijk rein...@netbsd.org
---
include/nilfs.h |1 -
lib/nilfs.c | 19
to this regression fix?
I don't know your applications actually do what. If you find mmap
calls for file IOs in strace analysis, this issue seems the likely
cause.
Thanks,
Ryusuke Konishi
--
To unsubscribe from this list: send the line unsubscribe linux-nilfs in
the body of a message to majord
Hi Linus,
please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git for-linus
This fixes a kernel oops on the rc1 and a data loss issue in mmap
write.
Thanks!
Ryusuke Konishi
--
The following changes since commit 0ce790e7d736cedc563e1fb4e998babf5a4dbc3d:
Linux
On Wed, 30 Mar 2011 13:07:46 +0200, Jens Axboe jax...@fusionio.com wrote:
On 2011-03-30 06:25, Ryusuke Konishi wrote:
diff --git a/fs/nilfs2/page.c b/fs/nilfs2/page.c
index 4d2a1ee..9d2dc6b 100644
--- a/fs/nilfs2/page.c
+++ b/fs/nilfs2/page.c
@@ -495,12 +495,14 @@ unsigned
On Wed, 30 Mar 2011 13:17:18 +0200, Jens Axboe wrote:
On 2011-03-30 13:07, Jens Axboe wrote:
On 2011-03-30 06:25, Ryusuke Konishi wrote:
diff --git a/fs/nilfs2/page.c b/fs/nilfs2/page.c
index 4d2a1ee..9d2dc6b 100644
--- a/fs/nilfs2/page.c
+++ b/fs/nilfs2/page.c
@@ -495,12 +495,14
: fix oops due to a bad aops initialization
Thanks,
Ryusuke Konishi
Mar 30 17:48:40 localhost kernel: BUG: unable to handle kernel NULL pointer
dereference at 0024
Mar 30 17:48:40 localhost kernel: IP: [c1088bd9]
try_to_release_page+0x26/0x3e
Mar 30 17:48:40 localhost kernel: *pdpt
Please consider including the attached patch to stable trees between
2.6.30 and 2.6.37.
This is the modified version of the following commit which is already
in upstream.
commit: 34094537943113467faee98fe67c8a3d3f9a0a8b
From: Ryusuke Konishi konishi.ryusuke at lab.ntt.co.jp
Date: Sun, 27 Mar
from
nilfs.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/file.c|1 -
fs/nilfs2/page.c| 53 +-
fs/nilfs2/page.h|4 -
fs/nilfs2/segbuf.c | 12
fs/nilfs2/segment.c | 153 ++-
fs
, but the cleaner daemon and
other nilfs tools no longer require it. This resolves problems that
occurs on the partitions where .nilfs was deleted, especially a stuck
problem on a disk full condition.
See changelog ( http://www.nilfs.org/download/ChangeLog-utils-v2 )
for details.
Thanks,
Ryusuke
The super root block is newly-allocated each time it is written back
to disk, so unused portion of the block should be cleared.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/inode.c | 10 ++
fs/nilfs2/segment.c |2 ++
include/linux
makes a difference ?
Thanks,
Ryusuke Konishi
---
From: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
nilfs_cleanerd: judge instantly deleted blocks as dead
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
sbin/cleanerd/cleanerd.c |3 +++
1 files changed, 3 insertions(+), 0
can be obtained as follows:
# dumpseg /dev/sda6 1721
~
your block device
where the segment 1721 contains the block 3526535 (a segment consists
of 2048 blocks by default). It doesn't contain any user private data.
Regards,
Ryusuke Konishi
---
Regards,
Ivan
...
B-tree node blocks, which appear without blkoff = X or with level =
X, are irrelevant to this error.
Thanks,
Ryusuke Konishi
Could you take summaries of the segment 1721 and its adjacent segments ?
Summaries of a segment can be obtained as follows:
# dumpseg /dev/sda6
the inconsistency.
Thanks,
Ryusuke Konishi
---
Regards,
Ivan Telichko
--
To unsubscribe from this list: send the line unsubscribe linux-nilfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from
On Fri, 29 Apr 2011 17:18:45 +0900, Ryusuke Konishi wrote:
This enlarges the region that a garbage collection lock protects so
that indivisible steps of garbage collection do not interleave.
Target segments are selected outside the critical section, so this
also reexamines the selected
, or cleanerd with an interrupt.
Thanks,
Ryusuke Konishi
--
To unsubscribe from this list: send the line unsubscribe linux-nilfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
into there.
Thanks,
Ryusuke Konishi
---
Ryusuke Konishi (2):
nilfs2: super root size should change depending on inode size
nilfs2: zero fill unused portion of super root block
--
To unsubscribe from this list: send the line unsubscribe linux-nilfs in
the body of a message to majord
The super root block is newly-allocated each time it is written back
to disk, so unused portion of the block should be cleared.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/inode.c | 10 ++
fs/nilfs2/segment.c |7 +--
2 files changed, 15
This adds resize ioctl which makes online resize possible.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/ioctl.c | 27 ++
fs/nilfs2/nilfs.h |1 +
fs/nilfs2/sufile.c| 67 +
fs/nilfs2
When shrinking the filesystem, segments to be truncated must be test
if they are busy or not, and unneeded sufile block should be deleted.
This adds routines for the truncation.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/sufile.c | 112
After resizing the filesystem, the secondary super block must be moved
to a new location. This adds a helper function for this.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/super.c | 57 +
1 files changed, 57
resizing is not yet available, and I'm feeling it needs some
more consideration.
The nilfs-resize tool is currently experimental, but the kernel
patches work fine so far. So, I'm planning to queue them for the next
merge window unless a critical problem arises.
Thanks,
Ryusuke Konishi
to allocate new segments from the range unless no free segments are
available there.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/ioctl.c | 34 +
fs/nilfs2/sufile.c| 73 ++--
fs/nilfs2
simply do it by going through a super block instance
like inode-i_sb-s_fs_info.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/bmap.c|4 +++-
fs/nilfs2/btnode.c |9 +
fs/nilfs2/gcinode.c |8
fs/nilfs2/inode.c |8
fs/nilfs2
In the current nilfs, page cache for btree nodes and meta data files
do not set a valid back pointer to the host inode in mapping-host.
This will change it so that every address space in nilfs uses
mapping-host to hold its host inode.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
These are cleanup patches for the next merge window, only internal
changes, and no enhancements are included.
Ryusuke Konishi
--
Ryusuke Konishi (5):
nilfs2: use empty_aops for gc-inodes
nilfs2: use list_first_entry
nilfs2: get rid of NILFS_I_NILFS
nilfs2: always set back
This replaces nilfs_mdt_mark_buffer_dirty and nilfs_btnode_mark_dirty
macros with mark_buffer_dirty and gets rid of nilfs_mark_buffer_dirty,
an own mark buffer dirty function.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/alloc.c | 12 ++--
fs/nilfs2
the regression.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/alloc.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/fs/nilfs2/alloc.c b/fs/nilfs2/alloc.c
index 0a0a66d..f768448 100644
--- a/fs/nilfs2/alloc.c
+++ b/fs/nilfs2/alloc.c
@@ -646,7
this type from a given
block offset of the metadata file.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/alloc.c | 35 +--
fs/nilfs2/alloc.h | 10 ++
2 files changed, 43 insertions(+), 2 deletions(-)
diff --git a/fs/nilfs2/alloc.c b
two checkpoints.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/bmap.c | 154 ++
fs/nilfs2/bmap.h | 15 +
2 files changed, 169 insertions(+), 0 deletions(-)
diff --git a/fs/nilfs2/bmap.c b/fs/nilfs2/bmap.c
maintains one parent inode and igore the hard
links.
Also, the size of parent inode numbers stored in the new field is
limited to 32-bit width even though inode number may become a 64-bit
value.
So, at this moment, this is only applicable for experimental purposes.
Signed-off-by: Ryusuke Konishi
On Wed, 18 May 2011 17:43:58 +0900, Jiro SEKIBA wrote:
Hi,
At Mon, 16 May 2011 18:05:13 +0900,
Ryusuke Konishi wrote:
This is an experimental patchset which adds new ioctl commands for
finding differences between two checkpoints (snapshots) efficiently.
One of the commands
deletion.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
---
fs/nilfs2/btree.c | 21 ++---
1 files changed, 14 insertions(+), 7 deletions(-)
diff --git a/fs/nilfs2/btree.c b/fs/nilfs2/btree.c
index fd4f05b..b2e3ff3 100644
--- a/fs/nilfs2/btree.c
+++ b/fs/nilfs2/btree.c
! ;-)
Okay, so non-regular files should be rejected for the config option ;)
The following patch will resolve this.
Thanks,
Ryusuke Konishi
---
From: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
nilfs_cleanerd: reject configuration file other than regular file
The current config file option
values for the interval parameters.
Thanks,
Ryusuke Konishi
if you give me some hints and I will try again tomorrow :)
Dima Tisnek
On 26 May 2011 11:32, dexen deVries dexen.devr...@gmail.com wrote:
Hi,
On Thursday 26 of May 2011 20:11:55 you wrote:
I'm testing nilfs2 and other
.
But, I think we have other approaches to think about before that with
regard to performance improvement. For example, applying extent to
DAT seems much more effective.
Thanks,
Ryusuke Konishi
Regards,
--
dexen deVries
[[[↓][→]]]
For example, if the first thing in the file is:
?kzy
Hi Linus,
please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/ryusuke/nilfs2.git for-linus
to receive the following bug fixes. These fix a reported bug and two
boundary condition bugs recently found in btree code.
Thanks,
Ryusuke Konishi
--
The following changes since commit
a reported bug and two
boundary condition bugs recently found in btree code.
Thanks,
Ryusuke Konishi
--
The following changes since commit
59c5f46fbe01a00eedf54a23789634438bb80603:
Linux 3.0-rc2 (2011-06-06 18:06:33 +0900)
are available in the git repository at:
git
101 - 200 of 546 matches
Mail list logo
