search for: inode

...d to try "--repair" ? (Last time I tried this one, it completely b0rked a filesystem, beyond repair, and my wife would kill me ifever I trash this one, for that''s her machine, so please help ! ;-)) root@PartedMagic:~# btrfsck /dev/sda6 checking extents checking fs roots root 258 inode 772 errors 400 root 258 inode 1025 errors 400 root 258 inode 1029 errors 400 root 258 inode 1056 errors 400 root 258 inode 1057 errors 400 root 258 inode 1125 errors 400 root 258 inode 1126 errors 400 root 258 inode 1548 errors 400 root 258 inode 3845 errors 400 root 258 inode 48006 errors 400 root...

struct timespec64 has unused bits in the tv_nsec field that can be used for other purposes. In future patches, we're going to change how the inode->i_ctime is accessed in certain inodes in order to make use of them. In order to do that safely though, we'll need to eradicate raw accesses of the inode->i_ctime field from the kernel. Add new accessor functions for the ctime that we can use to replace them. Signed-off-by: Jeff Layton...

...01, Andreas Dilger wrote: > > If this is the case, then all of the other zero initializations can be > > removed as well. I figured that if most of the fields were being > > zeroed, then ones _not_ being zeroed would lead to this problem. > > Other zero initializations in inode->u certainly can be > removed, but whether it's worth doing or not depends is a matter of > taste (recall the flamefest around Tigran's crusade against global > zero initializers several months ago ;-) Yes, but now it is common practise to remove any global zero inits. > T...

...monstrate this capability to myself before fully committing to this system as the primary data storage. I'm having some problems resizing an ext3 filesystem after I've resized the underlying logical volume. Following the ext3 resize, fsck spits out lots of errors like: Pass 1: Checking inodes, blocks, and sizes Group 49's inode table at 1605636 conflicts with some other fs block. Relocate<y>? no I believe that I'm following the correct procedure for resizing the filesystem. Any pointers greatly appreciated. Thanks. A complete transcript demonstrating this problem follo...

The following series of patches attempts to detach metadata I/O from struct inode. They are currently tied together pretty tightly. Metadata reads happen via the ocfs2_read_blocks() functions, writes via both jbd2 and ocfs2_write_blocks(). - Each inode has a cache of associated metadata blocks stored on its ip_metadata_cache member. The ocfs2_read/write_blocks() functions...

...????????? ? ? ? ? ? 20110817 Gluster version is 3.2.2-1ubuntu~ppa1~lucid1 on client (samba server) and the same but Natty on the nodes. It was upgraded from 3.2.1. What is this? If a client try to access it, it freezes up. This is in log: [2011-08-17 12:29:43.108100] W [inode.c:1035:inode_path] 0-w-vol/inode: no dentry for non-root inode 1996985: b45eeb9d-5481-41f8-828a-2850c51e754c [2011-08-17 12:29:43.108135] W [fuse-bridge.c:508:fuse_getattr] 0-glusterfs-fuse: 35186424: GETATTR 139724065350900 (fuse_loc_fill() failed) [2011-08-17 12:29:45.149772] W [inode.c:1035:in...

When the extended attribute namespace grows to a b-tree, the leaf clusters are organized by means of 'buckets'. Each bucket is 4K in size, regardless of blocksize. Thus, a bucket may be made of more than one block. fs/ocfs2/xattr.c has a nice little abstraction to wrap this, struct ocfs2_xattr_bucket. It contains a list of buffer_heads representing these blocks, and there is even an

Even though we allocate more, we should be updating inode i_size as per the arguments passed Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com> --- Changes from V1: We should update i_size only if actual_len and cur_offset are both larger than i_size. Otherwise if actual_len is < i_size and cur_offset > i_size we may end up...

...ation. See the following error messages for details: EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. kjournald starting. Commit interval 5 seconds EXT3-fs: md1: orphan cleanup on readonly fs ext3_orphan_cleanup: deleting unreferenced inode 2010087 ext3_orphan_cleanup: deleting unreferenced inode 259361 ext3_orphan_cleanup: deleting unreferenced inode 972510 ext3_orphan_cleanup: deleting unreferenced inode 2009841 ext3_orphan_cleanup: deleting unreferenced inode 2010102 ext3_orphan_cleanup: deleting unreferenced inode 2010079 ext3_orp...

I've been working on a patchset to change how the inode->i_ctime is accessed in order to give us conditional, high-res timestamps for the ctime and mtime. struct timespec64 has unused bits in it that we can use to implement this. In order to do that however, we need to wrap all accesses of inode->i_ctime to ensure that bits used as flags are appro...

add error check for ocfs2_read_locked_inode() call. Signed-off-by: Wengang Wang <wen.gang.wang at oracle.com> -- Index: inode.c =================================================================== --- inode.c (revision 149) +++ inode.c (working copy) @@ -118,6 +118,7 @@ struct inode *ocfs2_iget(struct ocfs2_su struct inode *inode = N...

...n the core direct I/O code is more like a counter given that the writers already have external serialization. This series removes it in favour of a simpler counter scheme, thus getting rid of the rw_semaphore non-owner APIs as requests by Thomas, while at the same time shrinking the size of struct inode by 160 bytes on 64-bit systems. The only nasty bit is that two filesystems (fat and ext4) have started abusing the lock for their own purposes. I''ve added a new rw_semaphore to the fat node structures to keep the current behaviour, and merged a patch from Jan Kara to remove the i_alloc_s...

...ing. So fix this in order to keep us from making free space cache look valid when it really isnt. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com> --- fs/btrfs/file.c | 66 ++++++++++++++++++++++++++------------------- fs/btrfs/free-space-cache.c | 9 +++++-- fs/btrfs/inode.c | 9 +++++-- fs/btrfs/ordered-data.c | 26 ++++++++++++------ fs/btrfs/ordered-data.h | 2 +- fs/btrfs/relocation.c | 7 ++++- 6 files changed, 78 insertions(+), 41 deletions(-) diff --git a/fs/btrfs/file.c b/fs/btrfs/file.c index 3591e8f..3c790ef 100644 --- a/fs/btrf...

...ntation of free space. Signed-off-by: Yan Zheng <zheng.yan@oracle.com> --- diff -urp 2/fs/btrfs/ctree.h 3/fs/btrfs/ctree.h --- 2/fs/btrfs/ctree.h 2010-04-26 17:28:20.493839748 +0800 +++ 3/fs/btrfs/ctree.h 2010-04-26 17:28:20.498830465 +0800 @@ -2419,6 +2419,9 @@ int btrfs_cont_expand(struct inode *inod int btrfs_invalidate_inodes(struct btrfs_root *root); void btrfs_add_delayed_iput(struct inode *inode); void btrfs_run_delayed_iputs(struct btrfs_root *root); +int btrfs_prealloc_file_range(struct inode *inode, int mode, + u64 start, u64 num_bytes, u64 min_size, + loff_t ac...

...are beyond the expected size of the file. This operation will spend lots of time if there are many dirty pages. It is also the only disadvantage of this patch. (Maybe I''m overcautious, we needn''t hold that data.) Signed-off-by: Miao Xie <miaox@cn.fujitsu.com> --- fs/btrfs/inode.c | 159 +++++++++++++++++------------------------------------- 1 files changed, 49 insertions(+), 110 deletions(-) diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index df6060f..9ace01b 100644 --- a/fs/btrfs/inode.c +++ b/fs/btrfs/inode.c @@ -88,7 +88,7 @@ static unsigned char btrfs_type_by_mod...

Hi all, this series removes most users of the write_one_page API. These helpers internally call ->writepage which we are gradually removing from the kernel. Changes since v2: - more minix error handling fixes Changes since v1: - drop the btrfs changes (queue up in the btrfs tree) - drop the finaly move to jfs (can't be done without the btrfs patches) - fix the existing minix code to

...hine. The only way to resolve the same I know is to do a sudo fsck -y /dev/sdb7 This is the output I got when I ran fsck through the Live CD $ sudo fsck -y /dev/sdb7 fsck 1.41.3 (12-Oct-2008) e2fsck 1.41.3 (12-Oct-2008) /dev/sdb7 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Inode 991290 has illegal block(s). Clear? yes Illegal block #12 (1770618119) in inode 991290. CLEARED. Illegal block #13 (3240613319) in inode 991290. CLEARED. Illegal block #14 (2657962509) in inode 991290. CLEARED. Illegal block #15 (1989131717) in inode 991290. CLEARED....

...) and it seems to be happy, except... As a test, I then filled the filesystem up, lastly copying /usr/bin (as root, so the filesystem became brim full). I then umounted it, and ran e2fsck -n -f /dev/hda6, and got the following: e2fsck 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09 Pass 1: Checking inodes, blocks, and sizes Inode 4113, i_blocks is 142, should be 64. Fix? no Inode 5902, i_blocks is 2, should be 0. Fix? no Inode 5903, i_blocks is 2, should be 0. Fix? no Inode 5904, i_blocks is 2, should be 0. Fix? no Inode 5905, i_blocks is 2, should be 0. Fix? no Inode 5906, i_blocks is 2, shou...

...with the acl-patches from acl.bestbits.at and the patches for the fileutils and e2fsprogs. If you need more informations please mail. ----------------------------------------------------------------------------- kernel says: Jul 24 11:34:13 o5s kernel: EXT3-fs error (device sd(8,10)) in ext3_new_inode: error 28 ----------------------------------------------------------------------------- fsck says: e2fsck 1.25 (20-Sep-2001) Warning! /dev/sda8 is mounted. Warning: skipping journal recovery because doing a read-only filesystem check. Pass 1: Checking inodes, blocks, and sizes Inodes that were pa...

...which is apparently a deadlock. The system is undergoing a filesystem stress test. The machine is pingable, but console and most other features are unresponsive. The console debugger can be accessed. The following information is available with db's "ps". I suspect the wchan of "inode" to be what everything is waiting on. I'm not sure who is supposed to perform the waking. db> ps pid proc addr uid ppid pgrp flag stat wmesg wchan cmd 467 e75df000 e76d6000 0 141 141 000104 3 inode c34ab600 sshd 466 e75df1a0 e76c9000 25 147 147 000...