for NFS exporting a cluster filesystem
are many - NFS clients are available for lots of platforms, some cluster
filesystems only work well tightly coupled, you want an HA NFS server,
you want an incrementally scalable NFS server, or some combination of these.
Cheers, Andreas
--
Andreas Dilger
changes are bundled with the start of the truncate/unlink,
where the inode information is changed.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.u
size of the device. With
something like LVM, there is no problem making a logical device of any
given size.
The journal will be identified in the filesystem by the journal_uuid, and
the journal will identify different client filesystems by the ext2 uuid.
Cheers, Andreas
--
Andreas Dilger
descriptors per block */
unsigned long s_groups_count; /* Number of groups in the fs */
struct buffer_head * s_sbh; /* Buffer containing the super block */
@@ -57,9 +57,6 @@
int s_desc_per_block_bits;
int s_inode_size;
int s_first_ino;
- int
because the layout of the filesystem itself hasn't really changed.
Note that you should build mke2fs on this older system, and it will turn
off the defaults for creating new filesystems with features enabled.
--
Andreas Dilger \ "If a man ate a pound of pasta and a pou
"class" (i.e. leading character) than other EAs. This was with the
intention of defining that class as "do not copy" when it became an issue.
This would solve the problem immediately.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta
broken in other ways). Heinz
decided to update the IOP instead. Note that with the new library build,
it is possible to have multiple IOP tools installed at the same time, and
the correct ones are chosen at runtime based on the kernel IOP.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a
ck but you
know that someone will want to dereference it later anyways when it
is invalid.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalga
Stephen, you write:
On Fri, Feb 23, 2001 at 01:20:40AM -0700, Andreas Dilger wrote:
At some time in the recent past, I was looking at the attribute checking
in ext2, and the following (ugly) piece of code didn't make sense.
ext2_notify_change isn't used in 2.4. It used to be unused
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
-
To unsubscribe from this list: send the line "unsubscrib
? The one that calls the "read_super" method.
AFAICT, only the first mount calls down to the FS anyways (the rest
is VFS internal).
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him
Al, you write:
On Tue, 13 Mar 2001, Andreas Dilger wrote:
"/mnt" from the first mount. If it comes to the point where I can get
that, then I will start to worry about "mount --bind".
This is to store in the ext2 on-disk superblock, which is currently always
(from
E).
Would it be possible to put a valid vfsmnt pointer in kern_mnt for
non-FS_SINGLE filesystems? Would only the vfsmnt information (maybe
d_path(kern_mnt, kern_mnt-mnt_mountpoint, buf, buflen)) be enough
to determine the pathname of the filesystem mount point?
Cheers, Andreas
--
Andr
, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
-
To unsubscribe from this list: send the line "un
Al writes:
On Thu, 22 Mar 2001, Andreas Dilger wrote:
I look forward to seeing the ext2 code. I was just in the process of
adding ioctls to ext3 to do online resizing within transactions. Maybe
I'll rather use this interface if it looks good. Will it work on 2.2,
or does it depend too
to only do 4kB block I/O on top of these devices
(not much of an issue for such large devices).
Still, this is just a stop-gap measure because next year people will want
16TB devices, and there won't be an easy way to do this.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of
ion I have read about problems with clean shutdown of a subsystem
that is used for rootfs, and finitrd would be a nice way to do so,
if possible. Comments?
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel o
could have corruption after a crash.
If they are not handled correctly, this would eventually this would lead
to overflows on a long-running filesystem and I doubt that happens.
Cheers, Andreas
--
Andreas Dilger Turbolinux filesystem development
http://sourceforge.net
Andrew writes:
Andreas Dilger wrote:
I still don't agree. If they are contiguous in the file (even if
we have 32 filesystem blocks in a page, then we are still only
dirtying a limited number of indirect blocks (5). Yes, we can dirty
up to 32 block bitmaps, 32 group descriptors, and 32
owner.
Any chance that the machines have been cracked, and people are playing
games with the system? Unlikely, but possible.
Cheers, Andreas
--
Andreas Dilger \ If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?
http://www
a global search-and-replace
for all of the jfs_* functions, and rename them jbd_*, to avoid
conflicts with IBM JFS.
Cheers, Andreas
--
Andreas Dilger \ If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?
http://www
an in-use filesystem is too twisted and dangerous, IMHO,
and a huge amount of effort for an extremely rare situation).
Cheers, Andreas
--
Andreas Dilger \ If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?
http://www
Malcolm Beattie writes:
Andreas Dilger writes:
PS - I used to think shrinking a filesystem online was useful, but there
are a huge amount of problems with this and very few real-life
benefits, as long as you can at least do offline shrinking. With
proper LVM usage
, it might reduce the
CPU usage. Did you check that at all?
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://members.shaw.ca/adilger/ http://members.shaw.ca/golinux/
pgpN4R7lZWxgG.pgp
Description: PGP signature
);
+ put_filesystem(type);
+ return mnt;
+}
This will OOPS if fstype is bad, since you unconditionally put_filesystem()
on a possible PTR_ERR() type. You need an extra
if (!IS_ERR(type))
put_filesystem(type);
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects
later (if the
VFS/VM doesn't discard the whole thing).
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://members.shaw.ca/adilger/ http://members.shaw.ca/golinux/
pgpFS2T2LxOPJ.pgp
Description: PGP signature
for another
EA...
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://members.shaw.ca/adilger/ http://members.shaw.ca/golinux/
pgpwmhI74h2Rc.pgp
Description: PGP signature
variables defined in only a subset
of the function. Could you verify with checkstack that this doesn't hit
here? Otherwise we need to move the common journal_head and buffer_head
allocations up to the main function declarations.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster
welcome putting forth any NFS related ...
Strange, group is called HECIWG, website is hecewg?
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL
that it is going to be
doing this (e.g. ls, GNU rm, find, etc) then why not let the filesystem
take advantage of this information? If combined with the statlite
interface, it can make a huge difference for clustered filesystems.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File
is a pipe dream.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
the whole thing to the server and returns everything in
one shot. That would imply everything would be at least as up-to-date
as the opendir().
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux
with readdirplus() also allows the filesystem to
do the stat() operations in parallel internally (which is a net win if
there are many servers involved) instead of serially as the application
would do.
Cheers, Andreas
PS - I changed the topic to separate this from the openfh() thread.
--
Andreas
of readdirplus(), and I think most people agree with
that part of it (though there is contention on whether readdirplus() is
needed at all).
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel
,
which also depends on st_mode.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
the config help.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Dec 15, 2006 14:37 -0800, Ulrich Drepper wrote:
Andreas Dilger wrote:
IMHO, once part of the information is optional, why bother making ANY
of it required? Consider ls -s on a distributed filesystem that has
UID+GID mapping. It doesn't actually NEED to return the UID+GID to ls
for each
, not for a directory.
So I will use my new ioctl.
Though it might make sense to implement FIBMAP for a directory, to keep
it consistent and allow user-space tools like filefrag to work on
directories also.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc
recently modified (e.g. within the last 30 minutes) in the default case,
on the assumption that they might be deleted soon anyways.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel
preallocation via fallocate/ioctl) so that
they don't have to zero-fill large files, or is there also automatic
preallocation of space to files (e.g. for O_APPEND files)?
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send
...
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
and it would be useful for files that were not preallocated.
For filesystems that don't implement punch glibc() would do zero-filling
of the punched area I guess (to make it equivalent to reading from a
hole in the file).
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems
. At that point you need to do a tar/untar
(or whatever) to copy the data instead of a raw partition copy.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL
determining how many RMW cycles the tail of an average I/O requires.
I'd guess a vast majority of IO will have the end similarly misaligned as
the start. Very little filesystem IO is 512 bytes, possibly excluding XFS
in an unusual mode.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
the mke2fs is enabling the dir_index feature by default now. This
shows dramatic performance improvements with 1 files per directory.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux
);
}
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
. It appears
to have been 2.6.11, but I don't know why.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
have been better to CC the filesystem maintainers directly
(which was one of the reasons Andrew wanted per-fs patches so they
can be Ack/Nack independently.
Looks good in any case,
Signed-off-by: Andreas Dilger [EMAIL PROTECTED]
diff -urpN -X dontdiff linux-2.6.21-rc6-mm1/fs/ext4/inode.c
linux
-mapped
filesystems, they can at least improve over the -bmap() case by skipping
holes in files that cover [dt]indirect blocks (saving thousands of calls).
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line
On Apr 12, 2007 12:22 +0100, Anton Altaparmakov wrote:
On 12 Apr 2007, at 12:05, Andreas Dilger wrote:
I'm interested in getting input for implementing an ioctl to
efficiently map file extents holes (FIEMAP) instead of looping
over FIBMAP a billion times. We already have customers
On Apr 16, 2007 18:01 +1000, Timothy Shimmin wrote:
--On 12 April 2007 5:05:50 AM -0600 Andreas Dilger [EMAIL PROTECTED]
wrote:
struct fiemap_extent {
__u64 fe_start; /* starting offset in bytes */
__u64 fe_len; /* length in bytes */
}
struct
On Apr 16, 2007 21:22 +1000, David Chinner wrote:
On Thu, Apr 12, 2007 at 05:05:50AM -0600, Andreas Dilger wrote:
struct fiemap_extent {
__u64 fe_start; /* starting offset in bytes */
__u64 fe_len; /* length in bytes */
}
struct fiemap
in
another chunk.
Also, is it considered a cross-chunk reference if a directory entry is
referencing an inode in another group? Should there be a continuation
inode in the local group, or is the directory entry itself enough?
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File
10.3 10.8 10.6; avg. 10.8
Start with blocks remapped with e2remapblocks:
13.5 15 13 14.5 14.5; avg. 14.1
(after remapping, data was stored in 20 continguous extents on disk)
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from
that the user can't access especially with FLAG_SYNC and/or
FLAG_HSM_READ.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
On Apr 30, 2007 08:09 -0400, Theodore Tso wrote:
On Fri, Apr 27, 2007 at 12:09:42PM -0600, Andreas Dilger wrote:
I'd prefer that such functionality be integrated with Takashi's online
defrag tool, since it needs virtually the same functionality. For that
matter, this is also very similar
On May 01, 2007 11:28 -0400, Theodore Tso wrote:
On Tue, May 01, 2007 at 12:01:42AM -0600, Andreas Dilger wrote:
Except one other issue with online shrinking is that we need to move
inodes on occasion and this poses a bunch of other problems over just
remapping the data blocks.
Well, I
On May 01, 2007 14:22 +1000, David Chinner wrote:
On Mon, Apr 30, 2007 at 04:44:01PM -0600, Andreas Dilger wrote:
Hmm, I'd thought offline would migrate to EXTENT_UNKNOWN, but I didn't
I disagree - why would you want to indicate the state is unknown when we know
very well
version numbers for the interface.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
no blocks allocated in the filesystem.
I don't think it makes the operation significantly more efficient than
say ioctl(DMAPI_FORCE_READ); ioctl(FIEMAP) if an application actually
needs the data to be present instead of just returning mapping info that
includes UNMAPPED.
Cheers, Andreas
--
Andreas
and more useful here.
Ouch, not very friendly error handling.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
-filling of the file in userspace.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
On May 07, 2007 19:02 -0400, Jeff Garzik wrote:
Andreas Dilger wrote:
Actually, this is a non-issue. The reason that it is handled for
extent-only is that this is the only way to allocate space in the
filesystem without doing the explicit zeroing.
Precisely /how/ do you avoid the zeroing
to deallocate unwritten extents in a safe manner.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
what they are.
It's like having a key to a door that you don't know where it is.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More
write() the
mtime/ctime will be updated, so it makes sense to be consistent for
both methods. Also, it just makes sense from the this file was modified
point of view.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send
On May 08, 2007 16:49 -0500, Serge E. Hallyn wrote:
Quoting Andreas Dilger ([EMAIL PROTECTED]):
One of the important use cases I can see today is the ability to
split the heavily-overloaded e.g. CAP_SYS_ADMIN into much more fine
grained attributes.
Sounds plausible, though it suffers
listed in the e2fsprogs repo.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
the return type needs
to also be an loff_t to match @len.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
doesn't check if the block layer can actually write to
a block device 2TB.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More
with a similar hash into nearby inodes, and this heuristic works
relatively well for that. Once the given leaf block's inode range is full
then new inodes can be allocated from a new window as it was done for the
newly-created directory.
Cheers, Andreas
--
Andreas Dilger
Principal Software
complete version of the ext3 journal checksumming
patch that avoids the need to do the pre-commit barrier, since the checksum
can verify at recovery time whether all of the transaction's blocks made
it to disk or not (which is what the commit block is all about in the end).
Cheers, Andreas
--
Andreas
a virtual EA like user.inode_version and have the kernel fill
this in from i_version.
Lustre will manipulate the ei-i_fs_version directly.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux
On May 31, 2007 17:11 -0700, H. Peter Anvin wrote:
NFS takes a binary option block anyway. However, that's the exception,
not the rule.
There was recently a patch submitted to linux-fsdevel to change NFS to
use text option parsing.
Cheers, Andreas
--
Andreas Dilger
Principal Software
requested == amount read/written and
don't even check whether that is actually the case or not.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED
. Not rebuilding empty parts of the fs, limit parity resync to parts
of the fs that were in the previous transaction, use fs-supplied checksums
to verify on-disk data is correct, use RAID geometry when doing allocations,
etc.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster
, 10);
This is probably a bad name for a mount option. What about order=10?
Otherwise you prevent any other option from being used in the future.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe
with increasing EXT{2,3,4}_MAX_BLOCK_SIZE to
32kB (AFAIK), but I haven't looked into this in a while.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL
. That is also useful for arches that have
PAGE_SIZE 4kb without this patchset.
Definitely, which is why we had been working on this originally.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel
at all.
On Mon, Jun 25, 2007 at 07:15:00PM +0530, Amit K. Arora wrote:
Implement new flags and values for mode argument.
This patch implements the new flags and values for the mode argument
of the fallocate system call. It is based on the discussion between
Andreas Dilger and David Chinner
existing data */
so that it doesn't imply this is only for DEALLOC.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
the file is not visibly changing. Maybe the
ctime update should be implicit if the size or mtime are changing?
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message
as at least one
of them makes it into the kernel.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
On Jun 26, 2007 16:15 +0530, Amit K. Arora wrote:
On Mon, Jun 25, 2007 at 03:52:39PM -0600, Andreas Dilger wrote:
In XFS one of the (many) ALLOC modes is to zero existing data on allocate.
For ext4 all this would mean is calling ext4_ext_mark_uninitialized() on
each extent. For some
the advocate for requirements David Chinner has put
forward due to existing behaviour in XFS. This is one of the reasons
why I think the flags mechanism we now have - we can encode the
various different behaviours in any way we want and leave it to the
caller.
Cheers, Andreas
--
Andreas Dilger
and there doesn't
seem to be any work to combine the two into a more powerful single layer.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More
it wouldn't be a problem.
That way we can allocate large swap files that don't need zeroing
in a single, fast operation, and hence potentially bring new
swap space online without needed very much memory at all (i.e.
should succeed in most near-OOM conditions).
Cheers, Andreas
--
Andreas Dilger
Any chance you can remove linux-fsdevel from the CC list? I don't think this
has anything to do with filesystems.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body
, size update, alloc/free, etc)
into monolithic modes that will never make everyone happy.
My understanding is that you only need to grab #4 and #7 to get your tree
into get fallocate in sync with the ext4 patch queue (i.e. they are
incremental over the previous set).
Cheers, Andreas
--
Andreas
a backup app to re-backup a file that was migrated via HSM):
FA_FL_NO_MTIME 0x10 /* keep same mtime (default change on size, data change) */
FA_FL_NO_CTIME 0x20 /* keep same ctime (default change on size, data change) */
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File
;
ext4_mark_inode_dirty(handle, inode);
mutex_unlock(inode-i_mutex);
return len - towrite;
Is this correct ? . Why do we set the qutoa file inodes version to 1
during write ?
Hmm, I thought we had previously fixed this?
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
-bit in-memory version anyway so using only the
low 32 bits of i_version in f_version is no more racy than in the past.
For 64-bit systems using the full on-disk i_version is possible.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from
to be a
transaction number). Instead of trying to incorporate this unused code
into ext4 we just turn off the ext4 version code and let Lustre control
this directly. It may even be that NFSv4 will need to control the version
numbers itself...
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster
that the high
bits of the seconds is handled correctly.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
into the superblock in s_flags is probably a good
idea. Kalpak, do you think you could get a patch that adds e.g.
EXT4_FLAGS_NO_INODE_VERSION (like EXT4_FLAGS_SIGNED_HASH in e2fsprogs).
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from
to
apply here?
Mostly, yes, but the name of the feature flag has changed.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
and e2fsck guarantee that
will be available in all in-use inodes, if RO_COMPAT_EXTRA_ISIZE is set
(ro-compat so that older kernels can't create inodes with a smaller
extra_isize). That feature is only enabled if requested by the sysadmin.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
to disable ext4 inode versioning by a flag the superblock,
but we dropped it at the last minute because it needed some updates and
we didn't want to wait on that for submitting these changes upstream.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc
On Jul 10, 2007 16:30 -0700, Andrew Morton wrote:
Signed-off-by: Mingming Cao [EMAIL PROTECTED]
Signed-off-by: Andreas Dilger [EMAIL PROTECTED]
Signed-off-by: Kalpak Shah [EMAIL PROTECTED]
---
Index: linux-2.6.21/include/linux/ext4_fs.h
1 - 100 of 145 matches
Mail list logo
