similar to: Assertion failure in journal_flush()

Hi all, We encountered a problem by chance today, a kernel bug which causes the following error: Assertion failure in journal_fl sh() at journal.c:1310: "!journal->j_running_transaction" kernel BUG at journal.c:1310! This happened while remounting an ext3 filesystem read-only. We often do this and haven't seen this bug before, so I suspect some kind of race. It

This version fixes three bugs in the 2nd patch of this series that caused kernel BUG when the system was under race. We weren't accounting with t_oustanding_credits correctly, and there were race conditions caused by the fact the I had overlooked the fact that __jbd2_log_wait_for_space() and jbd2_get_transaction() requires j_state_lock to be write locked. Theodore Ts'o (3): jbd2: Use

Hi, On Thu, Jan 24, 2002 at 04:54:34PM +0100, frode wrote: > > I got the following error while rm'ing a 700mb file from an ext3 partition: > > Assertion failure in journal_unmap_buffer() at transaction.c:1857: > "transaction == journal->j_running_transaction" Hmm --- this is not one I think I've ever seen before. > >>EIP; c015ea1a

Hi, as I mentioned in earlier mail to ext3-users I have been getting some corruption on an ext3 filesystem that has been serving NFS. I am now confident that I fully understand the problem and have a patch. It only affects data=journal mode and I wonder if it might also be the cause of the corruption noted by a number of people on linux-kernel. First I will explain the problem. Then display

The following 6 patches cleanup the jbd code and kill about 200 lines. First of 4 patches can apply to 2.6.13-git8 and 2.6.13-mm2. The rest of them can apply to 2.6.13-mm2. fs/jbd/checkpoint.c | 179 +++++++++++-------------------------------- fs/jbd/commit.c | 101 ++++++++++-------------- fs/jbd/journal.c | 11 +- fs/jbd/revoke.c | 158

Is there a way to find the holes in sparse files, other than assuming contiguous blocks of zeroes are holes? Thanks, Sean

Hi, We are trying to use OCFS2 as VM storage. After running into problems with qemu's disk_mirror feature we now think there could be a problem with the FIEMAP ioctl in OCFS2. As far as I understand the situation looks like this: Qemu inquiries the FS if the given section of the image is already allocated via the FIEMAP ioctl [1] It especially checks if fm_mapped_extents is greater 0.

I wonder if there would be anyone who would be willing to add extlinux support to RedHat's grubby program. From the looks of it, they already have grub, lilo, zipl, elilo, yaboot, and silo support, so I can't imagine it's that complex. -hpa

I have installed the xen 3.1.0 x86_64 tarball compiled for RHEL5 on a RHEL5 system. The system in question was able to boot with the xen kernel that came with RHEL5. I untarred the tarball, and did cd /boot mkinitrd /boot/initrd-2.6.18-xen.img 2.6.18-xen The command exited properly and made a initrd image. The machine booted with a grub.conf entry like this: title Xen 3.1.0 root

A small ext3 update. It fixes a few hard-to-hit but potentially serious problems. The patch is against 2.4.18-pre3, and is also applicable to 2.4.17. http://www.zip.com.au/~akpm/ext3-2.4-0.9.17-2418p3.gz 0.9.17 12 Jan 2002 ------------------- - Cleanup from Manfred Spraul which provides better randomisation of inode generation numbers. - A locking fix which prevents possible panics when

I have been having problems with syslinux not working on one system. The error message was "failed to create ldlinux.sys". I checked and mcopy was installed. But upon further investigation I finally found the problem. I were starting syslinux for python (2.4) and in the python code I made it ignore SIGNCHLD. It turns out that this signal state was inherited by syslinux and it made

When designing a filesystem, is fragmentation really an issue if access to the disk can be done using scatter-gather DMA techics ?

It seems to me that it should be possible to make --inplace and --sparse compatible. The manpage says -S, --sparse ... Conflicts with --inplace because it's not possible to overwrite data in a sparse fashion. but I think it _is_ possible to do that, provided the receiving side opens the dest file read-write instead of write-only. When writing within the existing

2017-10-25 17:28 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>: > 2017-10-24 12:58 GMT+03:00 Martin Kletzander <mkletzan@redhat.com>: >> On Fri, Oct 20, 2017 at 10:12:19PM +0300, Matwey V. Kornilov wrote: >>> >>> 2017-10-20 17:14 GMT+03:00 Matwey V. Kornilov <matwey.kornilov@gmail.com>: >>>> >>>> 2017-10-20 15:16

ocfs2 currently uses the Journaled Block Device (JBD) for its journaling. This is a very stable and tested codebase. However, JBD is limited by architecture to 32bit block numbers. This means an ocfs2 filesystem is limited to 2^32 blocks. With a 4K blocksize, that's 16TB. People want larger volumes. Fortunately, there is now JBD2. JBD2 adds 64bit block number support and some other

I'm writing a stackable file system and one of it's features is that it can combine many sparse files into a single view. On ext2/3 I was using bmap to give me the information needed, so for instance, if I created a big sparse file and tacked on some information at the end on ext2/3 I'd get something like blade12:~# ~/a.out abc File: abc Size: 30002 Blocks: 8 Blocksize: 4096 0

From: Carsten Otte <cotte at de.ibm.com> This patch adds Documentation/s390/kvm.txt, which describes specifics of kvm's user interface that are unique to s390 architecture. Signed-off-by: Carsten Otte <cotte at de.ibm.com> --- Documentation/s390/kvm.txt | 125 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 125 insertions(+) Index: kvm/Documentation/s390/kvm.txt

From: Carsten Otte <cotte at de.ibm.com> This patch adds Documentation/s390/kvm.txt, which describes specifics of kvm's user interface that are unique to s390 architecture. Signed-off-by: Carsten Otte <cotte at de.ibm.com> --- Documentation/s390/kvm.txt | 125 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 125 insertions(+) Index: kvm/Documentation/s390/kvm.txt

This is part of some patches to support sectors > 512. Currently I'm able to boot a Ubuntu kernel but seems that mboot is not working for some reason. This patch try to fix first stage of extlinux bootloader but have some problems with ADV Signed-off-by: Frediano Ziglio <frediano.ziglio at citrix.com> --- dos/syslinux.c | 2 +- extlinux/main.c | 36

On Wed, Oct 25, 2017 at 09:41:58PM +0300, Matwey V. Kornilov wrote: >Well, I really had to use start --console from the beginning. It would >have safe the time. > ># start --console s390_generic >Using guessed DASD geometry. > Using ECKD scheme (block size 4096), CDL > > ! >No