Displaying 20 results from an estimated 200 matches similar to: "[PATCH] fixup journal-related ifdef mess"
2008 Sep 04
4
[PATCH 0/3] ocfs2: Switch over to JBD2.
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
2003 Apr 18
2
kjournald panic in 2.4.20 RedHat 7.2
Hi, If this is a redundant post I apologize. I am running 2.4.20 on what has been
a very stable Athlon machine for months, tried to move a 2 GB file from an ext2
partition to an ext3 and kjournald crashed. Here are the last reminants of my
shell scrollback:
[*ROOT* mofo /mnt/sda1/mysql/fd 641 ] ll oldmail/
total 2363288
-rw-rw---- 1 mysql mysql 2147483647 Jan 23 18:04 maillog.MYD
2007 Jun 27
1
making new initrd, how to do it?
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
2003 Oct 27
2
EXT3 deadlock in 2.4.22 and 2.4.23-pre7 - quota related?
Hi all, and particularly Andrew and Stephen,
I recently "upgraded' one of my NFS fileservers from (patched)2.4.18
to 2.4.23-pre7 (in order to resolve a HIMEM related memory pressure
problem).
Unfortunately I have experienced what appears to be a deadlock.
The one I will describe was experienced while running 2.4.23-pre7,
though I had a very similar problem in 2.4.22 (but
2012 Apr 11
1
CentOS 5 - problem with kernel/process: task blocked for more than 120 seconds.
Hi All.
I have a server which hanged two times because we could not connect to the
box, it was not responding. In /var/log/messages I saw:
Apr 11 10:13:29 server kernel: INFO: task imap:5855 blocked for more than
120 seconds.
Apr 11 10:13:29 server kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Apr 11 10:13:29 server kernel: imap D
2003 Apr 18
0
kjournald panic in 2.4.20
Hi, If this is a redundant post I apologize. I am running 2.4.20 on what has been
a very stable Athlon machine for months, tried to move a 2 GB file from an ext2
partition to an ext3 and kjournald crashed. Here are the last reminants of my
shell scrollback:
[*ROOT* mofo /mnt/sda1/mysql/fd 641 ] ll oldmail/
total 2363288
-rw-rw---- 1 mysql mysql 2147483647 Jan 23 18:04 maillog.MYD
2004 Jul 16
1
Assertion failure in transaction.c
I am running Debian Potato with kernel 2.4.27-rc3 on a Sparc Server 20,
128MB RAM machine.
After few hours I get the following error in the syslog kernel file
Jul 15 01:09:25 mudshark kernel: Assertion failure in journal_stop() at
transaction.c:1418: "journal_current_handle() == handle"
Jul 15 01:09:25 mudshark kernel: kernel BUG at transaction.c:1418!
Jul 15 01:09:25 mudshark kernel:
2005 Nov 24
2
Assertion failure in ext3_sync_file() at fs/ext3/fsync.c:50: "ext3_journal_current_handle() == 0"
------------[ cut here ]------------
kernel BUG at fs/ext3/fsync.c:50!
invalid operand: 0000 [#1]
CPU: 0
EIP: 0060:[<b0187d38>] Not tainted VLI
EFLAGS: 00010296 (2.6.13.1)
EIP is at ext3_sync_file+0x58/0xf0
eax: 00000068 ebx: bf4a479c ecx: b03cffac edx: b03cffac
esi: b0398cfc edi: b2b8f1c8 ebp: c13bcf60 esp: c13bcf18
ds: 007b es: 007b ss: 0068
Process aptitude
2001 Jul 05
1
2.2.19/0.0.7a assertion failure
While ripping one of my cds on my laptop this happened:
Message from syslogd@theirongiant at Thu Jul 5 09:52:16 2001 ...
theirongiant kernel: Assertion failure in do_get_write_access() at transaction.c line 551: "handle->h_buffer_credits > 0"
from the kern.log:
Assertion failure in do_get_write_access() at transaction.c line 551: "handle->h_buffer_credits > 0"
2005 Aug 15
3
[-mm PATCH 2/32] fs: fix-up schedule_timeout() usage
Description: Use schedule_timeout_{,un}interruptible() instead of
set_current_state()/schedule_timeout() to reduce kernel size. Also use
helper functions to convert between human time units and jiffies rather
than constant HZ division to avoid rounding errors.
Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com>
---
fs/cifs/cifsfs.c | 7 ++-----
fs/cifs/connect.c
2004 Jun 06
1
[PATCH] use sb_getblk
It's both in 2.6 and recent 2.6 (for RH ASS2.1 you'll probably need to
copy the latest 2.4 defintion, but I don't care for obsolete junk).
Index: src/super.c
===================================================================
--- src/super.c (revision 1014)
+++ src/super.c (working copy)
@@ -799,7 +799,7 @@
/* get first two blocks */
for (i=0; i<2; i++) {
- bhs[i] = getblk
2011 Jun 24
10
[PATCH 0/9] remove i_alloc_sem V2
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
2002 Mar 27
1
assertion in journal_start
Hi,
I have a server configured as follows:
a standard 2.4.18 kernel, IDE discs, 1Gb RAM (not all used), load avg around 1-2.
a large partition, formatted reiserfs
within large partition are 80 300Mb loopback file systems, formatted ext3.
I got the following assertion yesterday which forced a lot of processes
into D state. I'm not sure how easy it is to reproduce this problem.
2017 Jul 26
2
[PATCH] virtio_blk: fix incorrect message when disk is resized
The message printed on disk resize is incorrect. The following is
printed when resizing to 2 GiB:
$ truncate -s 1G test.img
$ qemu -device virtio-blk-pci,logical_block_size=4096,...
(qemu) block_resize drive1 2G
virtio_blk virtio0: new size: 4194304 4096-byte logical blocks (17.2 GB/16.0 GiB)
The virtio_blk capacity config field is in 512-byte sector units
regardless of
2017 Jul 26
2
[PATCH] virtio_blk: fix incorrect message when disk is resized
The message printed on disk resize is incorrect. The following is
printed when resizing to 2 GiB:
$ truncate -s 1G test.img
$ qemu -device virtio-blk-pci,logical_block_size=4096,...
(qemu) block_resize drive1 2G
virtio_blk virtio0: new size: 4194304 4096-byte logical blocks (17.2 GB/16.0 GiB)
The virtio_blk capacity config field is in 512-byte sector units
regardless of
2010 Aug 04
6
[PATCH -v2 0/3] jbd2 scalability patches
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
2005 Jan 04
0
[PATCH] BUG on error handlings in Ext3 under I/O failure condition
Hello.
I found bugs on error handlings in the functions arround the ext3 file
system, which cause inadequate completions of synchronous write I/O operations
when disk I/O failures occur. Both 2.4 and 2.6 have this problem.
I carried out following experiment:
1. Mount a ext3 file system on a SCSI disk with ordered mode.
2. Open a file on the file system with O_SYNC|O_RDWR|O_TRUNC|O_CREAT
2014 May 29
3
[PATCH 0/2] UFS1/2 support series
From: Raphael S. Carvalho <raphael.scarv at gmail.com>
Wrote the documentation below. I think it would be good to push the doc to
the wiki as soon as the UFS support gets merged.
Unix Fast File System (UFS/FFS) 1/2 on Syslinux - (usage/install)
-----
There is a confusion about the name of this file system, then I decided to
contact the author who replied:
"The name has always been
2006 Jul 26
9
zfs questions from Sun customer
Please reply to david.curtis at sun.com
******** Background / configuration **************
zpool will not create a storage pool on fibre channel storage. I''m
attached to an IBM SVC using the IBMsdd driver. I have no problem using
SVM metadevices and UFS on these devices.
List steps to reproduce the problem(if applicable):
Build Solaris 10 Update 2 server
Attach to an external
2013 Jun 19
1
[PATCH] fs/jbd2: t_updates should increase when start_this_handle() failed in jbd2__journal_restart()
jbd2_journal_restart() would restart a handle. In this function, it
calls start_this_handle(). Before calling start_this_handle()?subtract
1 from transaction->t_updates.
If start_this_handle() succeeds, transaction->t_updates increases by 1
in it. But if start_this_handle() fails, transaction->t_updates does
not increase.
So, when commit the handle's transaction in