similar to: [PATCH] use sb_getblk

always use the 2.6 variants and fix up for 2.4 under the hood Index: src/journal.c =================================================================== --- src/journal.c (revision 1156) +++ src/journal.c (working copy) @@ -105,9 +105,17 @@ return status; } -#else -#define ocfs_journal_start journal_start -#define ocfs_journal_stop journal_stop + +#define journal_start(journal, nblocks) \ +

In a fit of irony, while preparing to burn a CDROM with some software I've been writing for about six months, I did a rm *>o instead of rm *.o on an ext3 filesystem. And I'm well aware that under normal circumstance you can't undelete, especially a ext3 filesystem. However, I need to at least *try* to recover this. I've built lde (linux disk editor) and if I can isolate a

Redhat 7.2 - ext3 filesystem. Is it possible to recover deleted files immediately after deleting them? I have found utilities for recovering data from ext2 filesystems... Help Regards Matt Cunningham Technology Manager Digital Post matt@digipost.co.nz

http://www.sample.banga.lt/crash.gif System - fully (except kernel) updated RedHat 7.3. Filesystems - ext3 in default ordered mode. What could be the cause of the crash? Kernel update will solve the problem? Thanks, Mindaugas

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

Hi. Sometimes I see much contention in smp_tlb_shootdown while running sysbench: sysbench --test=fileio --num-threads=8 --file-test-mode=rndrd --file-total-size=3G run kern.smp.cpus: 8 FreeBSD 7.1-R CPU: 0.8% user, 0.0% nice, 93.8% system, 0.0% interrupt, 5.4% idle Mem: 11M Active, 2873M Inact, 282M Wired, 8K Cache, 214M Buf, 765M Free Swap: 4096M Total, 4096M Free PID USERNAME PRI NICE

(vs format-changes branch) --- src/inc/ocfs_compat.h (revision 994) +++ src/inc/ocfs_compat.h (working copy) @@ -52,6 +70,8 @@ #define unlock_page(p) UnlockPage(p) #define Page_Uptodate(p) PageUptodate(p) +#define io_schedule schedule + #else /* LINUX_VERSION_CODE < 2.6 */ #define OCFS_GENERIC_SB_MEMBER(sb) ((sb)->s_fs_info) --- src/hash.c (revision 994) +++

I have a FreeBSD 4.8-Release machine that I upgraded from a 4.5 or 4.4 machine. It works just great for about 9 days, then processes will not die. It starts to become a problem when I can't kill processes, restart services, connections hang, and I can't reboot or shutdown, I have to do a hard reset. I can't really find anything in the logs to indicate what is giving me

I've been playing around with snapshots lately but I've got a problem on one of my servers running 7-STABLE amd64: FreeBSD paladin 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #8: Mon Nov 10 20:49:51 GMT 2008 tdb@paladin:/usr/obj/usr/src/sys/PALADIN amd64 I run the mksnap_ffs command to take the snapshot and some time later the system completely freezes up: paladin# cd /u2/.snap/ paladin#

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

---------- Forwarded Message ---------- Subject: ext3 for 2.4 Date: Thu, 17 May 2001 21:20:38 +1000 From: Andrew Morton <andrewm@uow.edu.au> To: ext2-devel@lists.sourceforge.net, "Peter J. Braam" <braam@mountainviewdata.com>, Andreas Dilger <adilger@turbolinux.com>, "Stephen C. Tweedie" <sct@redhat.com> Cc: linux-fsdevel@vger.kernel.org Summary:

I'm running 9.2-RC4 on a handful of desktop and server machines (both i386 and amd64). I have seen three panics (all vm_page_unwire) on one of those systems only (amd64 server) during the past week. The first two panics were triggered when shutting down the ntpd daemon (a recent development snapshot version of ntpd: 4.2.7p387). Exiting a later release (p388) has not triggered the panic.

Hi, here is the second version of OCFS2 quota fixes with Joel's comments fixed. Also I've added a patch defining counts of credits for quota operations as Joel asked. Honza

Hi, I did some more in-depth testing of OCFS2 quota code, especially with ECC feature enabled and spotted some problems. First four patches fix them. I need the fifth patch to be able to mount OCFS2 filesystem with 2.6.31-rc3. The sixth patch fixes a potential problem when quota syncing interval is updated while the cluster is running (which is not possible currently). Joel, could you please

Hello, This file server was upgraded from 6.2-RELEASE-p$something to 6.3-RELEASE-p3 (current RELENG_6_3 sources via csup) on August, 11 and rebooted to the new kernel on August, 12. The school is closed due to holidays. The only load is mail delivery to Maildirs via NFS from another server (just 50 mailboxes or so, none of them very busy) and nightly backups. I went there on August, 13 to perform

Signed-off-by: Alexey Dobriyan <adobriyan at mail.ru> Index: linux-2.6.10-bk11-warnings/fs/ext3/inode.c =================================================================== --- linux-2.6.10-bk11-warnings/fs/ext3/inode.c (revision 11) +++ linux-2.6.10-bk11-warnings/fs/ext3/inode.c (revision 12) @@ -803,7 +803,7 @@ if (create) { handle = ext3_journal_current_handle(); - J_ASSERT(handle

I'm getting oops whenever I pull a big file off of an ext3 filesystem on my large LV. The kernel this comes from happens to have lvm 1.0.2 and posix ACL for ext2/3 patched in, but I get the crash even on vanilla 2.4.17. kymoops 2.4.3 on i686 2.4.17-acl-lvm. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.17-acl-lvm/

A couple of years ago there was a discussion on lkml under the thread 'PATCH - ext2fs privacy (i.e. secure deletion) patch' about zapping deleted data in the filesystem as a security mechanism. The discussion wandered off into how 'chattr +s' could be implemented and whether encrypting filesystems wouldn't be a better solution to the problem. I've been maintaining a

When the extended attribute namespace grows to a b-tree, the leaf clusters are organized by means of 'buckets'. Each bucket is 4K in size, regardless of blocksize. Thus, a bucket may be made of more than one block. fs/ocfs2/xattr.c has a nice little abstraction to wrap this, struct ocfs2_xattr_bucket. It contains a list of buffer_heads representing these blocks, and there is even an

Every few days now I get a panic like the one shown in the attached backtrace. I've made sure my filesystem is clean with fsck and even turned off write caching on my IDE drive. Maybe someone here can figure out what is wrong. Let me know if you need more information. Michael -------------- next part -------------- root@taco /usr/src/sys/compile/ZOE> gdb -k -c /opt/savecore/vmcore.0