similar to: ext3+acl

A new work-in-progress release of the Extended Attribute and ACL patches for ext3 is now available at http://www.moldybread.net/patches/kernel-2.4/ This release is against linux-2.4.10-ac12 with ext3-2.4-0.9.12. Status: Extended attribute sharing now seems stable. Performance problems appear to have been addressed. Known Problems: Error message: "VFS: brelse: Trying to free free

Hello, I have today released an initial version of extended attributes and access control lists for ext3 (patch against the 2.4.13-ac3 kernel). Eric Jarman <ejarman@acm.org> has contributed a lot to this effort. Since I'm not very much into the innards of ext3, can some of you please take a look at the patch, and see whether it contains any flaws (and tell me which flaws)? Thanks! The

There is now a working patch for ACLs and Extended Attributes on kernel 2.4.x ext3 available at http://www.moldybread.net/patch/kernel-2.4 The patch applies over 2.4.9-ac3. The ac patch was used since it includes both ext3 and the new quota code. This patch has not yet been throughly tested. Known problems: 1. Extended attribute sharing does not work on ext3. Consistently causes crashes.

Hello, I'm attempting to create a smooth, 3D plot of a trajectory (rather than the cloud or wireframe functions). I would rather the individual data points not be visible. I've had no luck finding this on the graphics or help pages. Thank you in advance. Chris Some example data, just in case: 25 32 40 12 25 32 2 12 25 2 2 12 20 2 2 1 20 2 6 1 20 5 6 1 5 5 6

Has anyone tried LFS (ie >2G files support) and Ext3 together? Are there good reasons why this should/should not work? I see the RH enterprise kernel patch set specifically does not attempt both lfs and ext3, but the lfs patches themselves touch some reasonably localised parts of ext2, so I would hope (without having dived in there to test), that the ext3 changes would mirror that

In the Red Hat Linux spec file for the 2.2.19 kernel, there is a note not to enable ext3 and LFS at the same time. I'm wondering whether this is an old note, and that it is safe to use ext3 0.0.7a on a system with LFS enabled, or if there are still issues with it. I'm aware that 0.0.7a is a really old version, and 2.2 isn't the most modern kernel, but it is what I have to work with.

Hi, we're working on a stackable versioning file system for 2.4.x. Versioning can easily create lots of files for a file that gets modified frequently, and our current design puts all versions of a file in the same directory as the main file. We are therefore evaluating how stable and efficient different combinations of file systems would be in this scenario. We've run our versionfs on

We are using Samba Version 2.2.5 on a HP D Class Server running HP-UX 10.20. Anyway my question is does anybody happen to know what is the latest version of Samba that will operate with HP-UX 10.20? Regards Niall BancTec Limited. Registered Office: Jarman House, Mathisen Way, Poyle Road, Colnbrook, Berkshire SL3 0HF. Incorporated in England & Wales : 1283512. VAT : GB 228 4783 38.

Getting this oops on one of our production servers pretty much hangs the server. Do we have a corrupted Journal? how would ewe rebuild it? Any idea how to recover from it? Assertion failure in journal_bmap() at journal.c:636: "ret != 0" invalid operand: 0000 CPU: 0 EIP: 0010:[journal_bmap+70/96] Not tainted EIP: 0010:[<c016b646>] Not tainted EFLAGS: 00010282

Hi, Apologies in advance for any breaches of netiquette, I couldn't find any guidelines about submission to this forum but I'd be grateful for your help on something. My /boot filesystem is being remounted shortly after start-up as read-only. I get the following messages... journal_bmap_Ra7a5f568: journal block not found at offset 12 on ide0(3,1) Aborting journal on device ide0(3,1)

Hi Andrew, The patch below addresses the problem we were talking about earlier where ext3_writepage ends up accessing the inode after the page lock has been dropped (and hence at a point where it is possible for the inode to have been reclaimed.) Tested minimally (it builds and boots.) It makes ext3_journal_stop take an sb, not an inode, as its final parameter. It also sets

While compiling two kernels and untarring a third, my root fs was remounted r/w and I got the following in dmesg (kernel 2.4.19-pre9): EXT3-fs error (device ide0(3,2)) in ext3_new_inode: error 28 Aborting journal on device ide0(3,2). ext3_abort called EXT3-fs abort (device ide0(3,2)): ext3_journal_start: Detected aborted journal. Remounting filesystem read-only Remounting filesystem read-only

ext3 is having big problems on my x86-64 system. An ext3 partition has just gone crazy, with the following messages in dmesg: EXT3-fs error (device hda3): ext3_readdir: bad entry in directory #4603905: rec_len % 4 != 0 - offset=0, inode=2507704792, rec_len=42, name_len=0 Aborting journal on device hda3. ext3_abort called. EXT3-fs abort (device hda3): ext3_journal_start: Detected aborted journal

Hi there, I'm using RH7.2 (with the 2.4.9-30 kernal and it's required components) as a base for a server system running kernel 2.4.18. I've gone to this version to get around non-performing aic7xxx drivers in the stock 7.2 kernels, and updated gigabit ethernet drivers. I have a raid unit (Medea) attached to an Adaptec 3916, coming up as sdb. It has 2kb blocks, but the fault

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

No matter who I log in as, I always get the message, Password expires in 10 days. Checking the /etc/shadow file shows that it is set to 99999 which means it shouldn't expire. I am using Samba 2.2.2, Win2k with SP2 and all critical updates. I searched deja news for this problem and I couldn't find anyone else who is having this problem. Not that this matters, here is the log.jweber file

I think I have this one solved, I hope. I think what Andreas and I are running into are a few different assertions. One being the LVM lvm_do_pv_flush caused assertion which is related directly to invalidate_buffers() being called which then triggers refile_buffer() on a journaled buffer, which appears clean in all other ways according to the checks in refile_buffer(). The following is what

Hello everyone, I am probably not the only one having trouble with this package but here goes. I want to install XML on Ubuntu. I installed libxml2-dev and everything works out fine until I get the following: Error in reconcilePropertiesAndPrototype(name, slots, prototype, superClasses, : No definition was found for superclass "namedList" in the specification of class

Hello, I looked through the archives a bit and could not find anything relevant, if you know otherwise please point me in the right direction. I have a ~3T ext3 filesystem on linux software raid that had been behaving corectly for sometime. Not to long ago it gave the following error after trying to mount it: mount: wrong fs type, bad option, bad superblock on /dev/md0, or too many

Several people already reported this at linux-kernel and elsewhere with no answers, I thought perhaps this would be a more adequate forum... [1.] One line summary of the problem: After I/O, journal is aborted and filesystems made read-only. [2.] Full description of the problem/report: One can't anymore write to the affected file systems. Upon investigation, ext3fs journal was aborted