similar to: chattr +j ==> Oops

Hello I am on Athlon 1Gz, kernel 2.4.8. I was running a perl pgm with a lot of disk access, deletions and symlinks creations... Maybe It is due to the kernel version. Could you please inform me if must upgrade to a more recent kernel ? Thanks a lot the kernel logs are : in errors logs Oct 18 17:31:16 tadorne kernel: Assertion failure in journal_revoke_Rb5884a32() at revoke.c:307:

Hi, Doing the following I can generate an assertion in ext3 0.0.7a. I have an ext3 filesystem on /foo. I export /foo via nfs. I then mount via localhost:/foo onto /mnt. Start up a dd to generate a file on the nfs mount. (cd /mnt; dd if=/dev/zero of=./dd.out bs=1024k), then on the localhost filesystem /foo I rm the file. rm -f /foo/dd.out. This results in "ext3_free_inode: bit already

Hello all, I am trying to integerate 0.0.6b with our kernel RPM here and have come across an interesting conflict. I want to include the raid patch that Red Hat includes in their kernel but that patch includes the following hunk: --- linux/include/linux/fs.h.orig Tue Jan 16 13:30:09 2001 +++ linux/include/linux/fs.h Tue Jan 16 13:47:18 2001 @@ -191,6 +191,7 @@ #define BH_Req 3 /* 0 if the

I get 2 rejects applying 2.2.19-ext3 to latest errata rh 2.2.19 kernel. 1) fs/buffer.c Should I put "J_ASSERT(buf->b_count > 0);" before or after " *(int *)0 = 0;"? ===== ext3 0.0.7a patch --- 934,946 ---- if (buf->b_count) { buf->b_count--; + if (!buf->b_count && + (buf->b_jlist != BJ_None && buf->b_jlist

SYSTEM: rh6x based system, 2.2.19-6.2.7 rh errata kernel + 0.0.7a patch, I rebuilt rpm for i686; celeron466, 64MB, PIIX4. root fs is on software raid1 ext2, 6 additional fs's on software raid1 ext2. There's a 3rd HD, not mirrored, which is mounted ext3. EXT3-fs: mounted filesystem with ordered data mode. I enabled journal with tune2fs -j with unmounted fs. The 3 HDs are tuned with

Hi list, I just noticed in the chattr(1) man page that there exists a 'j' attribute which actually does the same thing that data=journal mount option would do, expect it only sets this property on the directories of my choice. Big Thanks to the one that came up with that idea :) It allows me to set +j on mail queues that must sit on the same partitions as the rest of the system (the guy

Hi Jason, I love your patch! Perhaps something to improve: [auto build test WARNING on net/master] url: https://github.com/0day-ci/linux/commits/Jason-Wang/Fix-various-issue-of-vhost/20181210-223236 config: i386-randconfig-x072-201849 (attached as .config) compiler: gcc-7 (Debian 7.3.0-1) 7.3.0 reproduce: # save the attached .config to linux build tree make ARCH=i386 All

All, I know that there is no official port to Kernel 2.4.4, thus I may not get any help, however I am hoping someone could point me in the right direction for my problem. I am currently forced to use kernel 2.4.4 for reasons out of my control (embedded board). Here are the exact versions of everything I'm running: ExT3 Version: ext3-2.4-0.9.6-248 Util Version: util-linux-2.11f.tar.bz2 e2fs

Hi Stephen, I'm one of developers of SnapFS, which based on Ext3. I got Assertion failure from SnapFS, at ext3_new_block() in fs/ext3/balloc.c: J_ASSERT (!test_and_set_bit(BH_Alloced, &bh->b_state)) If J_ASSERT is only use as debug, why it will modify data? I found the 'BH_Alloced' flag only occures at two place: one is balloc.c as above, the other is at journal_forget() in

We have DELL 2650 with CENTOS 3.4 installed. Today I saw following messages on /var/log/messages. Anyone know what it mean? Does it point to which disk? =================================== Jun 4 06:58:40 ORA03 kernel: EXT3-fs unexpected failure: (((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0); Jun 4 06:58:40 ORA03 kernel: Possible IO failure. Jun 4 06:58:40 ORA03 kernel:

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

> I''d think it would make more sense to store the PTE > that the grant has been bound to explicitly Already did that. > and hook the implicit unmap off of the pte update > validation code in Xen. I''m investigating your suggestion with a quick experiment. I put a hack into ptwr_do_page_fault(), which is one place where the pte address is available. The hack

When calling select.list(letters[1:3]) in a fresh R session (R v2.4.1, v2.5.0, v2.6.0 devel) on WinXP using *Rterm*, the dialog does *not* come up on front of other windows the first time you call it. Under Rgui it works just fine. If you do: 1) select.list(letters[1:3]) 2) bring the window to front manually 3) select an option and press OK 4) select.list(letters[1:3]) it the (second)

Postfix <http://www.postfix.org> does a chattr +S on its spool directory when it is installed on Linux. This is what is written in the postfix startup script -- # # LINUX by default does not synchronously update directories - # that's dangerous for mail. # if [ -f /usr/bin/chattr ] then CHATTR="/usr/bin/chattr +S" else CHATTR=echo fi -- Is this still required on ext3 ?

Hello, We have about 20 - 30 embedded machines running Linux 2.4.13, which the ext3-2.4-0.9.13-2413 patch applied. These are PowerPC 7410 based systems. I am getting reports of Oops happening either during removes (rm's), or coppies (cp's). Most reports state that issuing the same command once the system boots back up, does not cause it to crash. I guess its something else leading up

Hi, does someone else get this error message: Error in function (env) : could not find function "finalize"? I get an error when running examples in R CMD check (v2.6.0; session info below): > ### * invertMap > > flush(stderr()); flush(stdout()) > ### Name: invertMap > ### Title: Inverts a read or a write map > ### Aliases: invertMap > ### Keywords: file IO

Enabling compression via chattr +c works with ZLIB (default method) only, right? Since there is no way to specify a compression method. Cannot I use LZO this way? Thanks in advance, -- w -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

We run a third party application that creates an inordinate amount of subdirectories in a single directory. To speed up I/O, I wanted to set the T attribute on the directory that will hold the subdirectories. The "chattr +T /usr/local/lepus-bb/a-0607" command returns status 0, but when I verify the setting, the attribute isn't there: # lsattr -d /usr/local/lepus-bb/a-0607

What happens if you set an individual file inside a subvolume as nocow (chattr +C) and then take a snapshot of that subvolume and modify the file in both? Will btrfs now ignore the nocow attribute completely or will it do "as few copies as possible"? (I''d love to know if it''s possible to visualize the fragmentation of a single file.) -- To unsubscribe from this list:

postfix-users seems to be a subscription only list. I'd recommend incorporating TDMA <http://tdma.sf.net/> to allow for easy discussion by outsiders Andrew Morton (of ext3 fame) had sent this message to postfix-users list I am forwarding so that Wietse can hopefully provide the definitive answer to the question Andrew Morton/Stephen Tweedie seek ----- Forwarded message from Andrew