similar to: Reproducing fragmentation and out of space error

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

I have a setup with lot's of small files (Maildir), in 4 different volumes and for some reason the volumes are full when they reach 60% usage (as reported by df ). This was ofcourse a bit of a supprise for me .. lots of failed writes, bounced messages and very angry customers. Has anybody on this list seen this before (not the angry customers ;-) ? Regards, =paulv # echo "ls

Another simple question. How do I calculate the size of the volume from the superblock? Do I just use the two fields: u_int32_t s_blocksize_bits; /* Blocksize for this fs */ u_int32_t s_clustersize_bits; /* Clustersize for this fs */ What is the formula to use? Thanks, John

This is related to the "No space on OCFS2 volume" error discussed here this past Sep/Oct. Our Oracle support rep pointed us to Metalink note #1232702.1 and suggested we should script something up to periodically check the free contiguous blocks in the group chains for the volume in question. Reading the note, I get how to get Clusters per Group X Bits per Cluster from the "stat

Hi all. I have a 50 GB OCFS2 file system. I'm currently using ~26GB of space but df is reporting 43 GB used. Any ideas how to find out where the missing 17GB is at? The file system was formatted with a 16K cluster & 4K block size. Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello. I'm having issues using ocfs2 and drbd in dual primary mode. After running some filesystem test's that create a lot of small files I run really fast into "No space left on device" The non failing node is able to write/read from the filesystem. And the failing node is also able to delete/read from the filesystem Ubuntu custom kernel 2.6.27.2 o2cb_ctl version 1.3.9 drbd

Hi ALL I have a question about DISK space of OCFS2. I copy a file by a "cp" command after check the DISK space by "df -k" command. There is no change when I cheked the DISK space by "df -k"command again. I show below an procedure. ------------------------------------------------------------------------------- root at CPU_N:/fm/bbb> ls -l total 3 -rwxr-xr-x 1

Hello All, I have few questions around our use of ocfs1/2 for archive logs on 10G RAC. Is there an article out there describing why fragmentation is a special concern for ocfs1/2? Are there ways to remove fragmentation short of rebuilding the fs? Is there a way to estimate how often we will need to rebuild the fs? Any special tools/packages available to handle this issue? Regards, Pradeep.

The new code is dedicated to calculate free inodes number of all inode_allocs, then return the info to userpace in terms of an array. Specially, flag 'OCFS2_INFO_FL_NON_COHERENT', manipulated by '--cluster-coherent' from userspace, is now going to be involved. setting the flag on means no cluster coherency considered, usually, userspace tools choose none-coherency strategy by

Hi all, I'm testing OCFS2 as a cluster filesystem for a mail system based on maildir, so basically the filesystem must be able to deal with lots of directories, and lots of small files. The first "oddity", is that when I mount a newly formated ocfs2 fs, it already contains used space: [root@ocfs1 /]# df /cgp02 Filesystem 1K-blocks Used Available Use% Mounted on

Hi , I am getting the error "No space left on device" on a device with free space which is ocfs2 filesystem. Additional information is as below, [root at sai93 staging]# debugfs.ocfs2 -n -R "stats" /dev/sdb1 | grep -i "Cluster Size" Block Size Bits: 12 Cluster Size Bits: 15 [root at sai93 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release

For chdir03 investigation result: The fail is caused by the mkdir fail after setreuid. Key code in the test case: if ((pid =3D fork()) < 0) { tst_brkm(TBROK, cleanup, "first fork failed"); } if (pid =3D=3D 0) { /* first child */ /* set the child's ID to ltpuser1 */ if (setreuid(ltpuser1->pw_uid,

How can I check the amount on fragmentation on an OCFS2 volume? Thanks, Andy

Sorry, please pause this patch review. When I was investigating fstest generic failed case 347 361, I found the wake_up() action should move out the 'if()' area. The correct way is calling wake_up() unconditionally. Thanks, Heming On 4/21/23 4:36 PM, Heming Zhao wrote: > fstest generic case 266 272 281 trigger hanging issue when umount. > > I use 266 to describe the root cause.

fstest generic case 266 272 281 trigger hanging issue when umount. I use 266 to describe the root cause. ``` 49 _dmerror_unmount 50 _dmerror_mount 51 52 echo "Compare files" 53 md5sum $testdir/file1 | _filter_scratch 54 md5sum $testdir/file2 | _filter_scratch 55 56 echo "CoW and unmount" 57 sync 58 _dmerror_load_error_table 59 urk=$($XFS_IO_PROG -f -c "pwrite

Hi, we have recently started to use ocfs2 on some RHEL 5.5 servers (ocfs2-1.4.7) Some days ago, two servers sharing an ocfs2 filesystem, and with quite virtual services, stalled, in what it seems on ocfs2 issue. This are the lines in their messages files: =====node heraclito (0)======================================== /Dec 4 09:15:06 heraclito kernel: o2net: connection to node parmenides

Wayne.my vote is for a command-line option. I've noticed there is some penalty for very large files (35GB-50GB). The penalty is relatively small based on my 'intuitive' measurements.read me watching without running a real timer. The difference is very small compared to what happens after a few weeks without the fragmentation patch. Our SAN was becoming so fragmented that we were

[This email is either empty or too large to be displayed at this time]

mainly question for the intel folks, any chance to rerun the ltp testsuites to see how we are doing these days with all the changes ? thanks :) Wim

We are in the process of upgrading to OCFS2. We have recently restored our Production Database to a Development platform configured with OCFS2 with RMAN. No problems. As for the Production migration, we understand that you cannot mount an OCFS volume (our current configuration) with OCFS2. We are interested in mounting an EXT3 file system, performing a cold RMAN backup, copying the datafiles