search for: disk_alloc

Sorry i don`t copy everything: TEST-MAIL1# echo "ls //orphan_dir:0000"|debugfs.ocfs2 /dev/dm-0|wc debugfs.ocfs2 1.6.4 5239722 26198604 246266859 TEST-MAIL1# echo "ls //orphan_dir:0001"|debugfs.ocfs2 /dev/dm-0|wc debugfs.ocfs2 1.6.4 6074335 30371669 285493670 TEST-MAIL2 ~ # echo "ls //orphan_dir:0000"|debugfs.ocfs2 /dev/dm-0|wc debugfs.ocfs2 1.6.4 5239722 26198604

...the filesystem. [...] $ ./btrfs filesystem df --help usage: btrfs filesystem disk-usage [-k] <path> [<path>..] Show space usage information for a mount point(s). -k Set KB (1024 bytes) as unit $ ./btrfs filesystem df / Path: / Summary: Disk_size: 72.57GB Disk_allocated: 25.10GB Disk_unallocated: 47.48GB Logical_size: 23.06GB Used: 11.01GB Free_(Estimated): 55.66GB (Max: 59.52GB, Min: 35.78GB) Data_to_disk_ratio: 92 % Details: Chunk_type Mode Size_(disk) Size_(logical...

I've configured a text Xen system using ocfs2 1.4.1 as the shared filesystem to enable migration. So far the file based xen disk sharing is working well. Yesterday I tried to do a "xm save vm /ocfs2/vm.save" and I keep getting the following message: __ocfs2_file_aio_write:2185 ERROR: status = -14 The file created is only 9113 bytes long where it should be about 2 GB i.e.

...re thing. Do: $ strace -ff -o /tmp/save xm save .... Zip up the traces and attach to bugzilla. Lastly, is the guest hvm or pvm, 32-bit or 64-bit. From the packages the host machine appears to be 64-bit. Sunil Mushran wrote: > Enable some tracing: > > $ debugfs.ocfs2 -l ENTRY EXIT INODE DISK_ALLOC SUPER FILE_IO NAMEI AIO allow > > $ xm save .... > > $ debugfs.ocfs2 -l ENTRY EXIT deny INODE DISK_ALLOC SUPER FILE_IO NAMEI > AIO off > > File a bugzilla and attach the syslog. > > Brett Worth wrote: > >> Sunil Mushran wrote: >> >> >&g...

...ere is any chunk, the disk is not shown (solvable) - - this command need root capability (I use the BTRFS_IOC_TREE_SEARCH to get the chunk info; so that is unavoidable) ghigo@emulato:~$ sudo ./btrfs fi df /mnt/btrfs1/ [sudo] password for ghigo: Path: /mnt/btrfs1 Summary: Disk_size: 9.00GB Disk_allocated: 1.83GB Disk_unallocated: 7.17GB Used: 284.00KB Free_(Estimated): 6.76GB (Max: 8.54GB, min: 4.96GB) Data_to_disk_ratio: 75 % Allocated_area: Data,RAID0: Size:921.75MB, Used:256.00KB /dev/vdc 307.25MB /dev/vdb 307.25MB /dev/vdd 307.25MB Data,Si...

Hello, We have a 3-node cluster setup with ocfs2. Since friday one of the nodes went down and would not become clustermember after a reboot because it was unable to write to the ocfs2 filesystem. Message: no space left on device. There is plenty of diskspace though. No problem whatsoever to create a file / directory on the filesystem using one of the other nodes. Today one of the remaining

Hi all, I was intending on trying out gjournal on a new disk i've added in my desktop. I had a look to see what the most recent patch provided by Pawel and found http://people.freebsd.org/~pjd/patches/gjournal6_20061024.patch I created the directories as per Pawel's original post (http://lists.freebsd.org/pipermail/freebsd-fs/2006-June/001962.html) and the patch succeeded with no failed