search for: b_free

...) calling put_last_free(bh) on the device buffers (for buffers with b_count == 0 and not dirty), which must conflict somehow with what jfs expects of the state of a buffer. It seems we would not have this problem if bh->b_count was non-zero. What I'm just testing is checking if a buffer is B_FREE before calling refile_buffer() on it, and just doing journal_remove_checkpoint() on the buffer directly... Nope, still not enough - now I get an oops: [[[LVM is in the process of calling PV_FLUSH ioctl => invalidate_buffers()]]] Attempt to refile free buffer Unable to handle kernel NULL pointe...

...================================== --- fs/jfs/checkpoint.c.orig Thu Mar 1 16:35:40 2001 +++ fs/jfs/checkpoint.c Thu Mar 29 17:08:51 2001 @@ -106,8 +106,15 @@ lock_journal(journal); return 1; } - - if (!buffer_dirty(bh) && !buffer_jdirty(bh) && + + if (bh->b_dev == B_FREE) { + if (bh->b_cp_transaction) { + unlock_journal(journal); + journal_remove_checkpoint(bh); + lock_journal(journal); + return 1; + } + } else if (!buffer_dirty(bh) && !buffer_jdirty(bh) && bh->b_list != BUF_CLEAN) { unlock_journal(journal); ref...

...buffer journal lists getting badly corrupted if we allow > > those buffers to be reused. > > > Does the patch below (untested, uncompiled!) work? > > OK, I've applied the patch (removing my old check for buffer_jdirty()), > but leaving in the checks in jfs/commit.c for B_FREE buffer heads. This > should tell me right away if there are still buffers being freed from > underneath the journal, without oopsing my machine all the time. I tested the patch, but it didn't seem to help. Basically, I was running a kernel compile, and copying files into a different ex...

Hi, ext3-0.0.6a has been uploaded to ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ext3-0.0.6a.tar.gz and ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ext3-0.0.6a.tar.gz This version changes the way dirty buffers are marked to protect against device drivers which might block in the ll_rw_block() function. (Loop and lvm are examples.) It should also fix a rare but persistent report of

...pe-from <david@fromorbit.com>) id 1eYVpZ-0006Nj-61; Mon, 08 Jan 2018 22:43:05 +1100 Date: Mon, 8 Jan 2018 22:43:05 +1100 From: Dave Chinner <david@fromorbit.com> To: "Richard W.M. Jones" <rjones@redhat.com> Cc: linux-xfs@vger.kernel.org Subject: Re: statfs b_avail & b_free different if the filesystem is mounted readonly Message-ID: <20180108114305.GA16421@dastard> References: <20180108084450.GU2787@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180108084...

after install libguestfs_xfs, all results are: [using guestfish] guestfish -N fs:xfs -m /dev/sda1 statvfs / bsize: 4096 frsize: 4096 blocks: 24713 bfree: 23391 bavail: 23391 files: 51136 ffree: 51133 favail: 51133 fsid: 2049 flag: 4096 namemax: 255 [using virt-rescure] virt-rescue -a test1.img ><rescue> mount /dev/sda1 /sysroot ><rescue> stat -f /sysroot File: