similar to: ext3 nodump attribute inheritance

Al writes: > On Thu, 22 Mar 2001, Andreas Dilger wrote: > > If this is the case, then all of the other zero initializations can be > > removed as well. I figured that if most of the fields were being > > zeroed, then ones _not_ being zeroed would lead to this problem. > > Other zero initializations in inode->u certainly can be > removed, but whether it's

https://bugzilla.samba.org/show_bug.cgi?id=2810 ------- Additional Comments From wayned@samba.org 2005-06-21 09:20 ------- Created an attachment (id=1282) --> (https://bugzilla.samba.org/attachment.cgi?id=1282&action=view) Very preliminary nodump support Here is a patch that might work with FreeBSD (I have no way to test it to know for sure -- this is based on a patch for GNU tar

This patch contains the following cleanups: - there's no need for ext3_count_free() #ifndef EXT3FS_DEBUG - having prototypes for ext3_count_free() in two different headers is nonsense Signed-off-by: Adrian Bunk <bunk at stusta.de> --- fs/ext3/balloc.c | 2 -- fs/ext3/bitmap.c | 8 +++++++- fs/ext3/bitmap.h | 8 -------- fs/ext3/ialloc.c | 1 - 4 files changed, 7

Hello anybody, I have a Suse 7.2 Linux with Kernel 2.4.9, which is compiled by myself, and is running stable. Now I try to patch my sourcecode in the way you write on your homepage. But thier are two Proglems: 1. When I download the the file "ext3-2.4-0.9.6-249.gz" with my Windows, I get no packedfile, I get a Textfile?! -so gunzip would not work. 2. never the less, I tried to patch

While adding a file into orphan dir in ocfs2_orphan_add(), it calls __ocfs2_add_entry() before ocfs2_journal_access_di(). If ocfs2_journal_access_di() failed, the file is added into orphan dir, and orphan dir dinode updated, but file dinode has not been updated. Accordingly, the data is not consistent between file dinode and orphan dir. So, need to call ocfs2_journal_access_di() before

Ooops, last one didn't CC ocfs2-devel. On Mon, Oct 13, 2008 at 06:16:15PM -0700, Joel Becker wrote: > @@ -232,25 +231,17 @@ int ocfs2_populate_inode(struct inode *inode, struct ocfs2_dinode *fe, > ocfs2_mount_local(osb) || !ocfs2_stack_supports_plocks()) > use_plocks = 0; > > - /* this means that read_inode cannot create a superblock inode > - * today. change if

I'm not sure where else to ask about this, so please excuse me if this is the wrong forum. In trying to remove a 'nodump' flag on a directory with the 'chflags' command I have noticed that the 'nonodump' flag does not function. I see an open PR for the problem: o [2003/01/09] i386/46912 johan chflags nonodump fails I was wondering when this might be dealt with? Else is

I've been working on a patchset to change how the inode->i_ctime is accessed in order to give us conditional, high-res timestamps for the ctime and mtime. struct timespec64 has unused bits in it that we can use to implement this. In order to do that however, we need to wrap all accesses of inode->i_ctime to ensure that bits used as flags are appropriately handled. This patchset first

All, We are pleased to announce the release of OCFS2 1.4.10-1 and OCFS2 tools 1.6.3-2 for Oracle Linux 5 Update 7 and higher and Redhat Enterprise Linux 5 Update 7 and higher. Oracle's Unbreakable Linux Network users who are subscribing to the "OCFS2 1.4 packages for Enterprise Linux 5" channel can upgrade to this release by running up2date. Red Hat's Enterprise Linux 5

In snapshot destroy the dentry used for parent was the snapshot dentry itself. Remove d_invalidate since always return EBUSY, making possible to remove a snapshot using the btrfsctl -D option. Signed-off-by: Rui Miguel Silva <rmfrfs@gmail.com> --- fs/btrfs/ioctl.c | 7 ++----- 1 files changed, 2 insertions(+), 5 deletions(-) diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c index

hello hpa, please pull git pull git://brane.itp.tuwien.ac.at/~mattems/klibc.git maks for those changes: Kyle McMartin (1): klibc-utils: add dmesg maximilian attems (2): klibc comment fix fstype: add ocfs2 support with the following diffstat README | 2 usr/Kbuild | 2 usr/kinit/fstype/fstype.c | 15 +++++++

Hi ! Is a ext3 patch for kernel 2.4.14pre7 available ? Patching 2.4.14pre7 with latest patch ext3-2.4-0.9.14-2414p5 fails: patching file include/linux/sched.h Hunk #2 succeeded at 489 (offset 1 line). patching file include/linux/fs.h patching file include/linux/capability.h patching file fs/buffer.c patching file mm/filemap.c Hunk #1 succeeded at 209 (offset 4 lines). patching file mm/vmscan.c

hi, I set a file's inode.i_flags to "S_APPEND" in linux kernel, so the file can only be opened with 'append' mode. In linux system it works fine as expected. Like, echo "test" > append.txt, permission deny. echo "test" >> append.txt, OK. I share the directory to windows with samba server running on Ubuntu 14.4 and the directory is mounted as

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

On Wed, Mar 22, 2023 at 04:53:42PM +0100, Laszlo Ersek wrote: > The solution is that glibc *too* has a bug, and that bug hides the busybox bug. Namely, in glibc, going back to historical commit > > commit 6a032d81581978187f562e5533a32e0a6a3d352b (tag: cvs/libc-960210) > Author: Roland McGrath <roland at gnu.org> > Date: Sat Feb 10 10:00:27 1996 +0000 > > Sat Feb

On 3/22/23 15:45, Laszlo Ersek wrote: > On 3/21/23 18:28, Eric Blake wrote: > >> it is indeed a bug in busybox now that POSIX is moving towards >> standardizing realpath, so I've filed it: >> https://bugs.busybox.net/show_bug.cgi?id=15466 > > I've found another busybox bug. > > The "/bin/sh" utility is provided by busybox as well (via the

Alex pointed out the consequences after a transaction is not committed when a subvolume is deleted, so in case of a crash before an actual commit happens will let the subvolume reappear. Original post: http://www.spinics.net/lists/linux-btrfs/msg22088.html Josef''s objections: http://www.spinics.net/lists/linux-btrfs/msg22256.html While there''s no need to do a full commit for

Hi, First of all, I'm new to ocfs2 and drbd. I set up two identical servers (Athlon64, 1GB RAM, GB-Ethernet) with Debian Etch, compiled my own kernel (2.6.16.20), then compiled the drbd-modules and ocfs (modules and tools) from source. The process of getting everything up and running was very easy. I have one big 140GB partition that is synced with drbd (in c-mode) and has an ocfs2

Hi all, I am using OCFS2-1.4.7 for 2 servers which is running Red hat enterprise 5.7 kernel 2.6.18-274.el5. OCFS2 I use for drdb for replicating master-master. My 2 servers was installed HA-Proxy. Yesterday, server web1 was down with the log kernel panic. And today, web2 was down too. After that, I trace the log file on these server and found that the reason from ocfs2. The log

I have a 1.5 TB (1,475,720,773,632) partition that I wanted to convert from ext4 to btrfs. It is currently used as / for ubuntu 10.10. I booted into 11.04 beta2 and tried a ''btrfs-convert /dev/sdc1'', but after about 20 minutes it segfaulted. I performed a: sck.ext4 -cDfty -C 0 /dev/sdc1 After everything was clean, I downloaded the debugging symbols for btrfs-convert and