similar to: [BUGME 4683] oops at log_do_checkpoint+0xa1/0x230

Hi In ext3_get_parent(), quick string (struct qstr) can do the job, in place of declaring a dentry on stack. Following patch does this and saves few bytes on kernel stack. Thanks, Maneesh namei.c | 69 ++++++++++++++++++++++++++++++---------------------------------- 1 files changed, 33 insertions(+), 36 deletions(-) diff -urN linux-2.5.58-base/fs/ext3/namei.c

My manual patching of the rejects in checkpoint.c didn''t work out; a delete of 10,000 files caused a panic (in any ext fs, not just Lustre). In the new checkpoint.c, two routines expected by the patch no longer exist: __cleanup_transaction and __flush_buffer. I can avoid the panic if I omit (don''t try to manually patch) the following: Index: linux-2.6.9/fs/jbd/checkpoint.c

Hi, (I'm not too sure if this is the right list, perhaps samba-technical is more appropriate?) Has anyone taken a look at these bugs? http://bugme.osdl.org/show_bug.cgi?id=1671 http://bugme.osdl.org/show_bug.cgi?id=1732 Bug #1732 is my report, though #1671 has a very similar call trace so it may be the same bug and provide additional clues. I'm not too sure of the etiquette for

On Thu, Jan 19, 2006 at 08:38:47AM -0800, Bryan O'Sullivan wrote: > Yes. The code in the klibc tree has been sort of ready for that for > oh, about two years now. Thus far I'm very happy with it. I never originally intended to use klibc but I couldn't get the in-kernel DHCP code to work reliably in some cases and hacking it further didn't seem attractive at the time so I

I know smbfs is not samba, but perhaps somebody here has seen this error before. Basically, I can't use smbfs: [root@pandora samba]# mount //buildmaster/andreas -o username=andreas -t smbfs /mnt/smbfs added interface ip=10.0.17.30 bcast=10.0.23.255 nmask=255.255.248.0 error connecting to 10.0.16.6:445 (Connection refused) Password: [root@pandora samba]# ls -la /mnt/smbfs ls: /mnt/smbfs:

A little bugfix delta. I don't believe there is a need for x86 users to upgrade. http://www.uow.edu.au/~andrewm/linux/ext3/ - Fix unaligned access on Alpha - Fix build with CONFIG_JBD=n - Speed up log_do_checkpoint() - significant benefits for journalled data mode. - Fix possible oops in log_do_checkpoint(). - Comment out unused journal_release_buffer().

This caused a crash on a 2.6.10-1.12_FC2smp kernel May 19 09:56:35 spf1 kernel: Assertion failure in log_do_checkpoint() at fs/jbd/checkpoint.c:361: "drop_count != 0 || cleanup_ret != 0" May 19 09:56:35 spf1 kernel: ------------[ cut here ]------------ May 19 09:56:37 spf1 kernel: kernel BUG at fs/jbd/checkpoint.c:361! May 19 09:56:37 spf1 kernel: invalid operand: 0000 [#1] May 19

Hi, I have a data set with a continuous predictor X, a factor A and a continuous dependent variable Y. I am trying to build a linear model of the form: Y = (b0 + b1*X1)*B(A) where B(A) is a constant for each level of the factor A. I am not quite sure how to formulate the appropriate model formula. If I write: Y ~ ( 1 + X)/A , I get estimates for as many constants and slopes as the number of

(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Thu, 17 Feb 2011 13:20:20 GMT bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=29302 > > Summary: Null pointer dereference with large max_sectors_kb > Product: IO/Storage > Version: 2.5 > Kernel

Hi, We are running a server as an nfs head connect to a clariion, every couple of days we have our box fall over with the following msg in syslog. Has anyone had this happen to there boxen? rhel4 u4 May 8 12:23:52 ruchba kernel: Assertion failure in log_do_checkpoint() at fs/jbd/checkpoint.c:363: "drop_count != 0 || cleanup_ret != 0" May 8 12:23:52 ruchba kernel: ------------[ cut

I previously wrote: > I have come across what appears to be a bug in __invalidate_buffers() > w.r.t. the change in ext3-0.0.6 using BH_JDirty instead of BH_Dirty > for buffers held in the journal. If invalidate_buffers() is called > on a device (LVM likes to do this a lot, for whatever reason), it yanks > JDirty buffers out from underneath the journal layer, and causes an > oops

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

Hi all, back again, [Quick version] How do I concatenate two string to produce a third? Does the underlying representation of "character" allow this? [Long version] One thing I want to do with my database is to compare each record pairwise, without loading the whole database in memory....so I what I would like to do first query to get a list of strings which are the of the database

I previously wrote: > Stephen writes: > > I'd much rather fix the buffer.c code. Having journaling try to patch > > up after somebody has deleted its buffer heads is very wrong, since we > > risk the buffer journal lists getting badly corrupted if we allow > > those buffers to be reused. > > > Does the patch below (untested, uncompiled!) work? > >

Greetings, I have run into a kernel oops that I can generate at will, and that hangs my machine. The machine is running Gentoo Linux, 2.6.11 kernel and gcc 3.3.5. I can post more information if needed. The problem arises when I mount an SMB share from a 2000-series Snap server (network appliance); software version 3.4.804, hardware 2.0.3. The mount is fine, and can sit for a long time. However,

Dear R-enthusiasts, What a wonderful package R is, many thanks to all you have contributed (I've just started using it)...I have a few questions that I am having some trouble finding the answer to: I am using RPgSQL to grab some data from a postgresql database (about 179 columns and a few thousand rows), and I want to do a lot of pairwise comparison of the rows...(this is yeast genomic

On Thu, 10 Aug 2006 23:59:56 +0200 "Peter M" <peter.mdk@gmail.com> wrote: > The analyzer is a AMD Duron around 1200 MHz and has 128 MB of RAM. Your trying to squeeze blood from a turnip (not tulip) by trying to run 8 interfaces at once on that system. > I can't remember if the crashes only comes when I'm running tcpdumps > on several bridges at a time. But

Hi, I am getting the following Oops on 2.6.30.1 kernel. The bad part is, it happens rarely (twice in last 1.5 months) and the system is pretty lightly loaded when this happens (no heavy file/disk io). Any insights or patches that I can try? (i searched lkml and ext3 lists but could not find any similar oops/reports). == Oops =================== BUG: unable to handle kernel NULL pointer

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, I've recently been playing about with recent ext3 0.0.6b and lvm 0.9.1 beta7 and am now able to trigger an "Attempt to refile free buffer" assertion. This seems to "only" occur when using ext3 on the root filesystem. Possibly that is related to the fact that the lvm utility I'm using to reproduce this problem is modifying data in /etc. The easist reproduction