search for: unwritten

...nd write file access. Files are created by single writer (process) and can be read by multiple reader, possibly while the file is being written. 100+ different files may be written simultaneously, and can be read by 1000+ readers. I am currently using XFS on a local filesystem, preallocating the unwritten extents with RESVSP, writing and reading the files with large direct-io requests. OCFS2-1.3.9 appears to almost support the features I need. Large direct-io requests can be passed straight through to the storage device and allocation of unwritten extents are supported (even same API as XFS). Howe...

https://bugzilla.samba.org/show_bug.cgi?id=11588 Bug ID: 11588 Summary: missing option: preallocate for all files except for sparse Product: rsync Version: 3.1.2 Hardware: x64 OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: core

...Interval: 0 Last Check: Mon May 10 12:17:37 2010 Creator OS: 0 Feature Compat: 3 backup-super strict-journal-super Feature Incompat: 8016 sparse extended-slotmap inline-data metaecc xattr indexed-dirs refcount Tunefs Incomplete: 0 Feature RO compat: 1 unwritten Root Blknum: 5 System Dir Blknum: 6 First Cluster Group Blknum: 3 Block Size Bits: 12 Cluster Size Bits: 12 Max Node Slots: 10 Extended Attributes Inline Size: 256 Label: ocfs2disk UUID: B029D592BBB04D1ABA25111216009DD2 Has...

--- pxzcat.c | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/pxzcat.c b/pxzcat.c index 9bcdc36..55ccfc0 100644 --- a/pxzcat.c +++ b/pxzcat.c @@ -44,10 +44,11 @@ #include <sys/types.h> #include <error.h> #include <errno.h> #include <getopt.h> #include <pthread.h> +#include <linux/falloc.h> #include <lzma.h> #define DEBUG

The patch was created against a 1.4 tree. However, it applies cleanly to mainline too. The patch has been lightly tested. I am running fill_verify_holes on a non sparse volume currently. Please review. Sunil

Two patches follow this message. One fixes the default implementation of SEEK_HOLE/DATA. This patch applies atop Josef's last posted patch. The second patch implements the same on ocfs2. The test tool for the same is available here. http://oss.oracle.com/~smushran/seek_data/seek_test.c It is improved since the last post. It runs cleanly on zfs, ocfs2 and ext3 (default behavior). Users

Two patches follow this message. One fixes the default implementation of SEEK_HOLE/DATA. This patch applies atop Josef's last posted patch. The second patch implements the same on ocfs2. The test tool for the same is available here. http://oss.oracle.com/~smushran/seek_data/seek_test.c It is improved since the last post. It runs cleanly on zfs, ocfs2 and ext3 (default behavior). Users

The old extent merging code down underneath "ocfs2_mark_extent_written()" can't merge extents between leaf blocks. This patch resolve this. So that a large unwritten extent which has been split up with a bunch of writes can be merged together once all unwritten regions have been written to. Modification from V1 to V2: 1. Add more comments for some functions which is more complicated than before. 2. move the journal_access() calls to a better place so that we m...

...d define valid ways for the hypervisor to change it. "Pages hinted via VIRTIO_BALLOON_F_FREE_PAGE_HINT might get replaced by a zero page. However, as soon as the page is written by the guest (even before the hinting request was processed by the host), the modified page will stay - whereby the unwritten parts might either be from the old, or from the zero page." I think the debatable part is "whereby the unwritten parts might either be from the old, or from the zero page". AFAIU, you think it could happen in QEMU, that we have neither the old, nor the zero page, but instead some pr...

...tion directory: uwsgi requesting all changes adding changesets adding manifests adding file changes added 1169 changesets with 3532 changes to 332 files updating to branch default 278 files updated, 0 files merged, 0 files removed, 0 files unresolved Shouldn't the write behind cache be reading unwritten data before it hits the disk? Cheers Simon

...o corrupt guest memory. That leaves us with either 1. "Pages hinted via VIRTIO_BALLOON_F_FREE_PAGE_HINT might get replaced by zero page. However, as soon as the page is written by the guest (even before the hinting request was processed by the host), the modified page will stay - whereby the unwritten parts might either be from the old, or from the zero page." - a QEMU BUG. 2. "Pages hinted via VIRTIO_BALLOON_F_FREE_PAGE_HINT are considered unused and will contain an undefined/uninitialized content once hinted. As soon as the page is written by the guest (even before the hinting reque...

In __ocfs2_mark_extent_written, when we meet with the situation of c_split_covers_rec, the old solution just replace the extent record and forget to access and dirty the buffer_head. This will cause a problem when the unwritten extent is in an extent block. So access and dirty it. Signed-off-by: Tao Ma <tao.ma at oracle.com> --- fs/ocfs2/alloc.c | 27 ++++++++++++++++++++++++++- 1 files changed, 26 insertions(+), 1 deletions(-) diff --git a/fs/ocfs2/alloc.c b/fs/ocfs2/alloc.c index 54ff4c7..fcffc54 100644 --- a...

*** BLURB HERE *** Bean Huo (5): fs/buffer: clean up block_commit_write fs/buffer.c: convert block_commit_write to return void ext4: No need to check return value of block_commit_write() fs/ocfs2: No need to check return value of block_commit_write() udf: No need to check return value of block_commit_write() fs/buffer.c | 24 +++++++-----------------

Hi all, I upgraded ocfs from 1.2 to 1.4 after the update I launched tunefs.ocfs2 to enable the new ocfs2 features (sparse files and unwritten extents). tunefs.ocfs2 is now running since 2 days (12T partition) and I need my system back to production, can I safety abort tunefs.ocfs2? thanks Nicola

We have an application that has many processing threads writing more than a billion files ranging from 2KB ? 50KB, with 50% under 8KB (currently there are 700 million files). The files are never deleted or modified ? they are written once, and read infrequently. The files are hashed so that they are evenly distributed across ~1,000,000 subdirectories up to 3 levels deep, with up to 1000 files

...m was created: # xfs_info /store meta-data=/dev/sda5????????????? isize=256??? agcount=32, agsize=7454720 blks ???????? =?????????????????????? sectsz=512?? attr=0 data???? =?????????????????????? bsize=4096?? blocks=238551040, imaxpct=25 ???????? =?????????????????????? sunit=0????? swidth=0 blks, unwritten=1 naming?? =version 2????????????? bsize=4096 log????? =internal?????????????? bsize=4096?? blocks=32768, version=1 ???????? =?????????????????????? sectsz=512?? sunit=0 blks, lazy-count=0 realtime =none?????????????????? extsz=4096?? blocks=0, rtextents=0 The problem is reproducible and I don'...

This may be an unpopular opinion (and I don’t have the full context on those specific issues), but I believe that these are an abuse of XFAIL, and should probably be written in terms of REQUIRES instead of XFAIL. I believe XFAIL tests actually execute, and are just marked as expected failure. If a test is not expected to ever succeed, we shouldn’t bother running it, which is what the REQUIRES

One line fix from Joel's version. Also, some comments removed. 18:58 <sunil> wc->w_first_new_cpos = 18:58 <sunil> - ocfs2_align_bytes_to_clusters(inode->i_sb, i_size_read(inode)); 18:58 <sunil> + ocfs2_clusters_for_bytes(inode->i_sb, i_size_read(inode));

...gle_command(struct qxl_device *qdev, goto out_free_reloc; /* TODO copy slow path code from i915 */ - fb_cmd = qxl_bo_kmap_atomic_page(qdev, cmd_bo, (release->release_offset & PAGE_SIZE)); + fb_cmd = qxl_bo_kmap_atomic_page(qdev, cmd_bo, (release->release_offset & PAGE_MASK)); unwritten = __copy_from_user_inatomic_nocache - (fb_cmd + sizeof(union qxl_release_info) + (release->release_offset & ~PAGE_SIZE), + (fb_cmd + sizeof(union qxl_release_info) + (release->release_offset & ~PAGE_MASK), u64_to_user_ptr(cmd->command), cmd->command_size); { diff --git...

...pending" support for spec''s and steps is nice. I''m just wondering why a scenario itself can''t be pending? I.e. it seems to me like it would be nice to write up scenario titles for scenarios as you think of them, and for low-priority fringe scenarios leave the steps unwritten until it comes time to implement the scenario? Is there a way to add comments to the plain text file in plain text stories? Cheers, Tim. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/rspec-users/attachments/20080321/b626245d/attach...