similar to: ->journal_info sharing

If I patch the 2.4.14 kernel with the grsecurity patch first I get errors while patching the ext3 patch. the link for the grsecuritypatch is http://www.grsecurity.net/download.htm (which ever patch I do first works fine..the onther patch fails) this is the error I get fro patching the ext3 patch second (I get an error inthe same place if I patch the grsecurity patch second) Hunk #1 FAILED at

Hi all, Lustre 1.8.3 is available on the Sun Download Center Site. http://www.sun.com/software/products/lustre/get.jsp Our forwarding link has not yet been updated but should be shortly, so you can either find your way in through: http://www.sun.com/downloads/index.jsp?tab=2#L and look for Lustre 1.8.3 near the bottom of the "L" section. or

Hi all, Lustre 1.8.3 is available on the Sun Download Center Site. http://www.sun.com/software/products/lustre/get.jsp Our forwarding link has not yet been updated but should be shortly, so you can either find your way in through: http://www.sun.com/downloads/index.jsp?tab=2#L and look for Lustre 1.8.3 near the bottom of the "L" section. or

This patch finally gives us full proper -ENOSPC handling for btrfs. Now whenever you do a btrfs_start_transaction, you must specify the number of items you are planning to add/delete/modify. The worst case number of blocks that could be modified by changing that number of items will be calculated and checked against the amount of free space in the space_info where the root you are modifying

Hi I am hitting this Warning reproducible, the workload is a ceph osd, kernel ist 3.1.0-rc5. Best Regards, martin [ 5472.099766] ------------[ cut here ]------------ [ 5472.099833] WARNING: at fs/btrfs/inode.c:2193 btrfs_orphan_commit_root+0xb0/0xc0 [btrfs]() [ 5472.099838] Hardware name: MS-96B3 [ 5472.099842] Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit psmouse sp5100_tco

Hi all, Thanks for the prompt reply about 2.4.13. I applied the patch after I'd applied the win4lin and mki patches and it fails. The .rej file is included after this message. If you need any further info I'll try and supply it. Thanks Robyn This file is sched.h.rej from /usr/src/linux/include/linux/sched.h.rej *************** *** 399,404 **** u32 self_exec_id; /*

Hi all !!! I have got a MOSIX-Cluster and wanted to upgrade to ext3-fs, but that didn't work out. The ext3-fs patch FAILED to patch the MOSIX-kernel and if I tried to apply the ext3- patch before, the MOSIX-patch failed. Can someone help me with that ? Perhaps someone knows of a conclusion for that problem or can tell me where to get a MOSIX-patch for 2.4.15. I would be glad to hear from

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.

The freeze rwsem is taken by sb_start_intwrite() and dropped during the commit_ or end_transaction(). In the async case, that happens in a worker thread. Tell lockdep the calling thread is releasing ownership of the rwsem and the async thread is picking it up. Josef and I worked out a more complicated solution that made the async commit thread join and potentially get a later transaction, but

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

I am having some trouble compiling ext3 for the 2.4.13 kernel. It appears that the journaling source file is corrupted: In file included from sysctl.c:33: /src/linux-2.4.13/include/linux/jbd.h: In function `buffer_jbd': /src/linux-2.4.13/include/linux/jbd.h:241: `BH_JBD' undeclared (first use in this function) /src/linux-2.4.13/include/linux/jbd.h:241: (Each undeclared identifier is

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:

If we flush inodes with pending delalloc in a transaction, we may join the same transaction handler more than 2 times. The reason is: Task use_count of trans handle commit_transaction 1 |-> btrfs_start_delalloc_inodes 1 |-> run_delalloc_nocow 1 |-> join_transaction 2 |-> cow_file_range 2 |-> join_transaction 3 In fact, cow_file_range needn''t

I hope this EIP can enlightend the developers: Jun 10 10:28:59 shawarma kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000019 Jun 10 10:28:59 shawarma kernel: printing eip: Jun 10 10:28:59 shawarma kernel: c0181d47 Jun 10 10:28:59 shawarma kernel: *pde = 00000000 Jun 10 10:28:59 shawarma kernel: Oops: 0000 [#1] Jun 10 10:28:59 shawarma kernel: Modules linked in:

Hello List, Running 2.4.21-pre3-ac1 SMP with new quotas (usr and grp), this oops showed up while copying a large amount (about 50gigs, only 1.6 made it before the oops). I'm trying to reproduce as we speak. Unable to handle kernel NULL pointer dereference at virtual address 00000004 c0130956 *pde = 00000000 Oops: 0002 CPU: 0 EIP: 0010:[<c0130956>] Not tainted Using defaults

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 all, This is an alternative approach to atomic user transactions for btrfs. The old start/end ioctls suffer from some basic limitations, namely - We can''t properly reserve space ahead of time to avoid ENOSPC part way through the transaction, and - The process may die (seg fault, SIGKILL) part way through the transaction. Currently when that happens the partial transaction will

This series adds an initial implementation for scrub. It works quite straightforward. The usermode issues an ioctl for each device in the fs. For each device, it enumerates the allocated device chunks. For each chunk, the contained extents are enumerated and the data checksums fetched. The extents are read sequentially and the checksums verified. If an error occurs (checksum or EIO), a good copy

Hi all. Every few days I am getting a message that looks like the one I have cut and pasted below. It is accompanied by a severe slowdown of the system. In fact, it's practically locked. The machine runs gnome-desktops for 40 users plus about a hundred sessions of a curses based point of sale software, plus a few other functions, so it's a busy machine. Dual Xeon 3.2GHz processors.

Does anyone know how to diagnose the error "Unable to handle kernel paging request at virtual address xxxxxx"? I got this error (followed by a panic and a crash) on a server running CentOS 4.4 with the 2.6.9-42.0.8.ELsmp kernel. The machine is based on an Intel 975XBX2 motherboard (975X chipset). I have built several of these and they have been extremely stable. This one is