search for: inodes

Hi there, I have a system on which btrfsck gives the following output... I don''t understand the meaning of the reported errors, so any clue would be appreciated. Is this something I should worry about, or not ? Would I be advised 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,

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 <jlayton at kernel.org> --- fs/inod...

Al writes: > On Thu, 22 Mar 2001, 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

...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 follow...

...ead_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 take a struct inode to access this member. - The journal mostly doesn't care about inodes. It does, however, need to set the transaction id on the inode so that dlmglue knows when an inode needs to checkpoint. - All the metadata I/O paths use ip_io_mutex to synchronize their actions against each other. The problem is that if someone wants to use our metadata I/O facilities, the...

hi! One of our user removed a directory through samba and right after that recreated it. It looks like this now: ?????????? ? ? ? ? ? 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

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 setting wrong i_size value

...an_cleanup: deleting unreferenced inode 2009823 ext3_orphan_cleanup: deleting unreferenced inode 2009856 ext3_orphan_cleanup: deleting unreferenced inode 2009807 ext3_orphan_cleanup: deleting unreferenced inode 2009799 ext3_orphan_cleanup: deleting unreferenced inode 2009794 EXT3-fs: md1: 27 orphan inodes deleted EXT3-fs: recovery complete. It's my array: $ df -h Filesystem Size Used Avail Use% Mounted on /dev/md1 9.5G 735M 8.3G 8% / /dev/md7 38G 6.7G 30G 19% /var /dev/md6 15G 4.5G 9.1G 33% /usr /dev/md5 103G 45G 5...

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 appropriately handled. This patchset first

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 = NULL; struct super_block *sb = osb->sb; struct

i_alloc_sem has always been a bit of an odd "lock". It''s the only remaining rw_semaphore that can be released by a different thread than the one that locked it, and it''s use case in 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

I noticed that if the free space cache has an error writing out it''s data it won''t actually error out, it will just carry on. This is because it doesn''t check the return value of btrfs_wait_ordered_range, which didn''t actually return anything. So fix this in order to keep us from making free space cache look valid when it really isnt. Thanks, Signed-off-by:

...-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 actual_len, u64 *alloc_hint); extern...

The original truncation of btrfs has a bug, that is the orphan item will not be dropped when the truncation fails. This bug will trigger BUG() when unlink that truncated file. And besides that, if the user does pre-allocation for the file which is truncated unsuccessfully, after re-mount(umount-mount, not -o remount), the pre-allocated extent will be dropped. This patch modified the relative

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, shoul...

...-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 part of a corrupted orphan linked list found. Fix? no Inode 13 was part of the orphaned inode list. IGNORED. Inode 14 was part of the orphaned inode list. IGNORED. Inode 32807 was part of the orphaned inode list. IGNORED. Inode 49250 was part of the orphaned...

We have a reproducible problem with FreeBSD-4.7 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.