This workaround is not for you, man mkfs.ocfs2 and look the option

      -T filesystem-type
              Specify how the filesystem is going to be used, so that
mkfs.ocfs2 can chose optimal filesystem parameters for that use.  The
supported  filesystem  types
              are:

                   mail   Appropriate for file systems that will host lots
of small files.

                   datafiles
                          Appropriate for file systems that will host a
relatively small number of very large files.

                   vmstore
                          Appropriate for file systems that will host
Virtual machine images.



2013/8/7 "M.Atıf CEYLAN" <meh...@atifceylan.com>

>  Count: 243   Next Free Rec: 243
>  ##   Total        Used         Free         Block#
>         0    4096         4096         0            7878657
>         1    4096         4096         0            11997697
>         2    4096         4095         1            12126721
>         3    4096         4095         1            12158977
>         4    4096         4094         2            933889
>         5    4096         4096         0            326657
>         6    4096         4096         0            327681
>         7    4096         4096         0            12417025
>         8    4096         4094         2            329729
>         9    4096         4091         5            1224193
>         10   4096         4090         6            1288705
>         11   4096         4089         7            1320961
>         12   4096         4096         0            1385473
>         13   4096         4096         0            1449985
>
> Perhaps, I must increase the cluster size of ocfs2 :(
> Is the discontig-bg a workaround for me? If it's a workaround I'll make
> creation new volumes with big block size and move the data to there.
>
> What is your suggestion to me for mkfs.ocfs2 params? Journal size, cluster
> size etc.?
> (I have 6 volumes and each size is 140GB)
>
>
> On 08/07/2013 03:49 PM, emmanuel segura wrote:
>
>  Ok
>
>  Try with this:
>
> debugfs.ocfs2 -n -R "stat //inode_alloc:0000"
> Verify that the value "Next Free Rec" is at 0 and the value of either 0 Free
>
> This indicates that there is no 'more' contiguous space available to the 
> allocation of new blocks even if there 'space available on the system
>
> The solution to the problem of the allocation of blocks and 'to activate
> FEATURES discontig-bg that allows you to allocate non-contiguous spaces.
>
> The FEATURES you enable 'in this way
>
>  tunefs.ocfs2 --fs-features=discontig-bg
>
>
>
>
>
>
>
> 2013/8/7 "M.Atıf CEYLAN" <meh...@atifceylan.com>
>
>>  lot of free space
>>
>>
>> On 08/07/2013 03:41 PM, emmanuel segura wrote:
>>
>> df -k?
>>
>>
>> 2013/8/7 "M.Atıf CEYLAN" <meh...@atifceylan.com>
>>
>>> On 08/07/2013 02:55 PM, Jochen Spieker wrote:
>>>
>>>> "M.Atıf CEYLAN":
>>>>
>>>>> I have 2 Dovecot servers (as clustered on ocfs2). I sometimes get
>>>>> some errors since I installed the sieve plugin.
>>>>> Sometimes though they are not actually quota exceeded, I get "Quota
>>>>> exceeded" error messages.
>>>>> There is no any disk or file system error/warning.
>>>>>
>>>> Where do you expect such a warning to show up? Did you check all
>>>> relevant filesystems with "df -k" and "df -i"?
>>>>
>>>> J.
>>>>
>>>  Inodes are 63% used (max value of results). These errors shown in
>>> dovecot logs.
>>>
>>>
>>> --
>>> M.Atıf CEYLAN
>>> Yurdum Yazılım
>>>
>>>
>>>   --
>>> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a
>>> subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
>>> Archive: http://lists.debian.org/52023a13.9020...@atifceylan.com
>>>
>>>
>>
>>
>> --
>> esta es mi vida e me la vivo hasta que dios quiera
>>
>>
>>
>> --
>> M.Atıf CEYLAN
>> Yurdum Yazılım
>>
>
>
>
> --
> esta es mi vida e me la vivo hasta que dios quiera
>
>
>
> --
> M.Atıf CEYLAN
> Yurdum Yazılım
>



-- 
esta es mi vida e me la vivo hasta que dios quiera

Reply via email to