search for: xfs_io

.../0x98 [ 1998.478275] [<ffffffff8112200f>] vfs_write+0xaf/0x102 [ 1998.478275] [<ffffffff8112347e>] ? fget_light+0x3a/0xa1 [ 1998.478275] [<ffffffff81122222>] sys_write+0x4d/0x74 [ 1998.478275] [<ffffffff8146fec2>] system_call_fastpath+0x16/0x1b [ 2160.937580] INFO: task xfs_io:22734 blocked for more than 120 seconds. [ 2160.953899] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2160.978494] xfs_io D 0000000000000000 0 22734 21963 0x00000000 [ 2160.996597] ffff88000ac8dc68 0000000000000046 ffff88000ac8dc08 ffffffff0...

Hey all, Ok, so I've been having some trouble for a while with an EC2 instance running CentOS 5.11 with a disk volume reporting 100% usage. Root is on an EBS volume. So I've tried the whole 'du -sk | sort -nr | head -10' routine all around this volume getting rid of files. At first I was getting rid of about 50MB of files. Yet the volume remains at 100% capacity. Thinking

Add xfs_info to show the geometry of the xfs filesystem. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- Hi Rich, This patch add xfs_info, and start the xfs support work. I'd like to add the xfs support, like xfs_growfs, xfs_io, xfs_db, xfs_repair etc. Any thoughts? Thanks, Wanlong Gao daemon/Makefile.am | 1 + daemon/xfs.c | 69 ++++++++++++++++++++++++++++++++++++++++++ generator/generator_actions.ml | 6 ++++ src/MAX_PROC_NR | 2 +- 5 files changed, 78 insertions(+),...

...equire_dm_flakey + +rm -f $seqres.full + +_clean_working_dir() +{ + _mount_flakey + rm -rf $SCRATCH_MNT/* + _unmount_flakey +} + +# Btrfs wasn''t making sure the directory survived fsync +_directory_test() +{ + echo "fsync new directory" + _mount_flakey + mkdir $SCRATCH_MNT/bar + $XFS_IO_PROG -c "fsync" $SCRATCH_MNT/bar + _load_flakey_table $FLAKEY_DROP_WRITES + _unmount_flakey + + _load_flakey_table $FLAKEY_ALLOW_WRITES + _mount_flakey + _ls_l $SCRATCH_MNT | tail -n +2 | awk ''{ print $1, $9 }'' + _unmount_flakey + _check_scratch_fs $FLAKEY_DEV + [ $? -ne...

..., only root can write that last bit. most modern file systems suffer from severe fragmentation if you completely fill them. ext*fs, you adjust this with `tune2fs -m 1 /dev/sdXX`. XFS treats these reserved blocks as inviolable, so they don't show up as freespace, they can be changed with xfs_io but should be modified at your own risk. -- john r pierce 37N 122W somewhere on the middle of the left coast

...is a typo in __btrfs_prealloc_file_range() where we set the i_size to actual_len/cur_offset, and then just set it to cur_offset again, and do the same with btrfs_ordered_update_i_size(). This fixes it back to keeping i_size in a local variable and then updating i_size properly. Tested this with xfs_io -F -f -c "falloc 0 1" -c "pwrite 0 1" foo stat''ing foo gives us a size of 1 instead of 4096 like it was. Thanks, Signed-off-by: Josef Bacik <josef@redhat.com> --- fs/btrfs/inode.c | 9 +++++---- 1 files changed, 5 insertions(+), 4 deletions(-) diff --git a...

...00007efd6b0ed8e0 R08: 00000000000000e7 R09: ffffffffffffff98 [ 2504.186418] R10: 00007ffcac9bddb8 R11: 0000000000000246 R12: 00007efd6b0ed8e0 [ 2504.186419] R13: 00007efd6b0f2c20 R14: 0000000000000060 R15: 000000000070e705 [ 2504.186421] NMI backtrace for cpu 3 [ 2504.226980] CPU: 3 PID: 6596 Comm: xfs_io Not tainted 5.1.0+ #1 [ 2504.227661] Hardware name: ChromiumOS crosvm, BIOS 0 [ 2504.228261] Call Trace: [ 2504.228552] <IRQ> [ 2504.228795] dump_stack+0x46/0x5b [ 2504.229180] nmi_cpu_backtrace+0x89/0x90 [ 2504.229649] ? lapic_can_unplug_cpu+0x90/0x90 [ 2504.230157] nmi_trigger_cpumask...

...00007efd6b0ed8e0 R08: 00000000000000e7 R09: ffffffffffffff98 [ 2504.186418] R10: 00007ffcac9bddb8 R11: 0000000000000246 R12: 00007efd6b0ed8e0 [ 2504.186419] R13: 00007efd6b0f2c20 R14: 0000000000000060 R15: 000000000070e705 [ 2504.186421] NMI backtrace for cpu 3 [ 2504.226980] CPU: 3 PID: 6596 Comm: xfs_io Not tainted 5.1.0+ #1 [ 2504.227661] Hardware name: ChromiumOS crosvm, BIOS 0 [ 2504.228261] Call Trace: [ 2504.228552] <IRQ> [ 2504.228795] dump_stack+0x46/0x5b [ 2504.229180] nmi_cpu_backtrace+0x89/0x90 [ 2504.229649] ? lapic_can_unplug_cpu+0x90/0x90 [ 2504.230157] nmi_trigger_cpumask...

...write that last bit. most modern file systems > suffer from severe fragmentation if you completely fill them. ext*fs, you > adjust this with `tune2fs -m 1 /dev/sdXX`. XFS treats these reserved blocks > as inviolable, so they don't show up as freespace, they can be changed with > xfs_io but should be modified at your own risk. > > > > > > -- > john r pierce 37N 122W > somewhere on the middle of the left coast > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org...

...+0x9a/0xf0 [ 413.409157] [<ffffffff8104e2d7>] ? remove_wait_queue+0x3a/0x3a [ 413.409157] [<ffffffff8110386f>] vfs_write+0xc2/0x18f [ 413.409157] [<ffffffff81103c5b>] SyS_write+0x50/0x78 [ 413.409157] [<ffffffff8161fdc6>] system_call_fastpath+0x1a/0x1f [ 413.409157] xfs_io D ffffffff00000001 0 4750 4746 0x00000000 [ 413.409157] ffff88007726fd68 0000000000000086 ffff88007c5a00b0 ffff88007726ffd8 [ 413.409157] 0000000000004000 0000000000012c80 ffffffff81c11410 ffff88007caf6d00 [ 413.409157] ffff88007726fca8 ffffffff810c072e ffff8800767396c0 ffff88...

...0e7 R09: > ffffffffffffff98 > [ 2504.186418] R10: 00007ffcac9bddb8 R11: 0000000000000246 R12: > 00007efd6b0ed8e0 > [ 2504.186419] R13: 00007efd6b0f2c20 R14: 0000000000000060 R15: > 000000000070e705 > [ 2504.186421] NMI backtrace for cpu 3 > [ 2504.226980] CPU: 3 PID: 6596 Comm: xfs_io Not tainted 5.1.0+ #1 > [ 2504.227661] Hardware name: ChromiumOS crosvm, BIOS 0 > [ 2504.228261] Call Trace: > [ 2504.228552] <IRQ> > [ 2504.228795] dump_stack+0x46/0x5b > [ 2504.229180] nmi_cpu_backtrace+0x89/0x90 > [ 2504.229649] ? lapic_can_unplug_cpu+0x90/0x90 > [...

On 5/14/19 7:54 AM, Pankaj Gupta wrote: > + if (!list_empty(&vpmem->req_list)) { > + req_buf = list_first_entry(&vpmem->req_list, > + struct virtio_pmem_request, list); > + req_buf->wq_buf_avail = true; > + wake_up(&req_buf->wq_buf); > + list_del(&req_buf->list); Yes, this change is the right one, thank you! > + /* > + * If

On 5/14/19 7:54 AM, Pankaj Gupta wrote: > + if (!list_empty(&vpmem->req_list)) { > + req_buf = list_first_entry(&vpmem->req_list, > + struct virtio_pmem_request, list); > + req_buf->wq_buf_avail = true; > + wake_up(&req_buf->wq_buf); > + list_del(&req_buf->list); Yes, this change is the right one, thank you! > + /* > + * If

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