search for: inode_alloc

...g-2007 22:01 . 34 drwxr-xr-x 6 0 0 4096 16-Aug-2007 22:01 .. 35 -rw-r--r-- 1 0 0 0 16-Aug-2007 22:01 bad_blocks 36 -rw-r--r-- 1 0 0 851968 16-Aug-2007 22:01 global_inode_alloc 37 -rw-r--r-- 1 0 0 65536 16-Aug-2007 22:01 slot_map 38 -rw-r--r-- 1 0 0 1048576 16-Aug-2007 22:01 heartbeat 39 -rw-r--r-- 1 0 0 249999654912 16-Aug-2007 22:01 global_bitmap...

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-co...

...2646 Symptoms for this bug include inability to create a file from some nodes while being able to do so from others. This problem is typically encountered when the disk free space is low. The reason for the inconsistent behavior is because inodes are allocated from a nodeslot specific system file, inode_alloc, that is dynamically extended when it runs out of free space. However, when disk free space is low, the chances that the filesystem is unable to grow this system file increases. Under this condition, only nodes that have free space in their slot specific inode_alloc are able to create new files....

...2646 Symptoms for this bug include inability to create a file from some nodes while being able to do so from others. This problem is typically encountered when the disk free space is low. The reason for the inconsistent behavior is because inodes are allocated from a nodeslot specific system file, inode_alloc, that is dynamically extended when it runs out of free space. However, when disk free space is low, the chances that the filesystem is unable to grow this system file increases. Under this condition, only nodes that have free space in their slot specific inode_alloc are able to create new files....

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 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

Recently I ran into a situation where an ocfs2 (1.4) volume was reporting it was out of space when it was not. Deleting some files helped short term but the problem quickly comes back. I believe this is due to the fragmentation bug that I have seen references to in the mailing list archive. I am trying to reproduce the problem on a test system so that I can validate that upgrading to 1.6

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

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 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

...any "inode allocator" space are free on every node? And when it's low how to check a chance go grow up "inode allocator" in current condition? ps: Version: Debian 4.0 and OCFS2 from official package v 1.2.1. I know about some improvements in current version (about stealing inode_alloc from other nodes etc.) and about newer package in Debian 5.x, but today I can't shut down cluster for so long and can't risk any problems during and after upgrade. ps2: sorry for my poor english Best regards -- ----------------------------------------------------------------------- S?a...

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

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

Hi, I'm sending a series of patches implementing quota support into ocfs2-tools. It's the same as the original huge patch I've sent but now it's split as Joel asked. I've also realized that when disabling SPARSE feature, we should update quota information. That piece of code is missing, I'll implement it soon. Comments welcome. Honza

Hi, this is the next version of quota support for quota tools. I've addressed all the comments of Tao, Joel and others. Sparse feature disabling also correctly updates quota information now and the patch is merged into the tunefs support patch. Honza

Hi, below comes a new version of the series of patches implementing quota support for ocfs2-tools. I've fixed the calls of ocfs2_malloc_blocks() which were given number of bytes instead of number of blocks. Besides that the series should be the same. Honza

Hi, This is the second batch of Ocfs2 patches intended for the merge window. The 1st batch were sent out previously: http://lkml.org/lkml/2008/12/19/280 The bulk of this set is comprised of Jan Kara's patches to add quota support to Ocfs2. Many of the quota patches are to generic code, which I carried to make merging of the Ocfs2 support easier. All of the non-ocfs2 patches should have