Displaying 9 results from an estimated 9 matches for "8357m".
Did you mean:
357m
2018 Apr 14
2
Getting glusterfs to expand volume size to brick size
...t/pylon_block1
/dev/sdc 26079M
1491M 23241M 7% /mnt/pylon_block2
/dev/sde 25071M
1491M 22315M 7% /mnt/pylon_block3
localhost:/dev_apkmirror_data 8357M
581M 7428M 8% /mnt/dev_apkmirror_data1
localhost:/dev_apkmirror_data 8357M
581M 7428M 8% /mnt/dev_apkmirror_data2
localhost:/dev_apkmirror_data 8357M
581M 7428M 8% /mnt/dev_apkmirror_data3
gluster volume i...
2018 Apr 16
2
Getting glusterfs to expand volume size to brick size
...: /dev/sde
Mount Options : rw,relatime,data=ordered
Inode Size : 256
Disk Space Free : 23.0GB
Total Disk Space : 24.5GB
Inode Count : 1638400
Free Inodes : 1625433
What's interesting here is that the gluster volume size is exactly 1/3 of
the total (8357M * 3 = 25071M). Yet, each block device is separate, and the
total storage available is 25071M on each brick.
The fstab is as follows:
/dev/disk/by-id/scsi-0Linode_Volume_pylon_block1 /mnt/pylon_block1 ext4
defaults 0 2
/dev/disk/by-id/scsi-0Linode_Volume_pylon_block2 /mnt/pylon_block2 ext4
defaults...
2018 Apr 16
0
Getting glusterfs to expand volume size to brick size
...sdc 26079M
> 1491M 23241M 7% /mnt/pylon_block2
> /dev/sde 25071M
> 1491M 22315M 7% /mnt/pylon_block3
> localhost:/dev_apkmirror_data 8357M
> 581M 7428M 8% /mnt/dev_apkmirror_data1
> localhost:/dev_apkmirror_data 8357M
> 581M 7428M 8% /mnt/dev_apkmirror_data2
> localhost:/dev_apkmirror_data 8357M
> 581M 7428M 8% /mnt/dev_apkmirror_...
2018 Apr 17
5
Getting glusterfs to expand volume size to brick size
...: 256
>> Disk Space Free : 23.0GB
>> Total Disk Space : 24.5GB
>> Inode Count : 1638400
>> Free Inodes : 1625433
>>
>>
>>
>> What's interesting here is that the gluster volume size is exactly 1/3 of
>> the total (8357M * 3 = 25071M). Yet, each block device is separate, and the
>> total storage available is 25071M on each brick.
>>
>> The fstab is as follows:
>> /dev/disk/by-id/scsi-0Linode_Volume_pylon_block1 /mnt/pylon_block1 ext4
>> defaults 0 2
>> /dev/disk/by-id/scsi-0Linod...
2018 Apr 17
0
Getting glusterfs to expand volume size to brick size
...ata=ordered
> Inode Size : 256
> Disk Space Free : 23.0GB
> Total Disk Space : 24.5GB
> Inode Count : 1638400
> Free Inodes : 1625433
>
>
>
> What's interesting here is that the gluster volume size is exactly 1/3 of
> the total (8357M * 3 = 25071M). Yet, each block device is separate, and the
> total storage available is 25071M on each brick.
>
> The fstab is as follows:
> /dev/disk/by-id/scsi-0Linode_Volume_pylon_block1 /mnt/pylon_block1 ext4
> defaults 0 2
> /dev/disk/by-id/scsi-0Linode_Volume_pylon_block2 /m...
2018 Apr 17
0
Getting glusterfs to expand volume size to brick size
...: 23.0GB
>>> Total Disk Space : 24.5GB
>>> Inode Count : 1638400
>>> Free Inodes : 1625433
>>>
>>>
>>>
>>> What's interesting here is that the gluster volume size is exactly 1/3
>>> of the total (8357M * 3 = 25071M). Yet, each block device is separate, and
>>> the total storage available is 25071M on each brick.
>>>
>>> The fstab is as follows:
>>> /dev/disk/by-id/scsi-0Linode_Volume_pylon_block1 /mnt/pylon_block1 ext4
>>> defaults 0 2
>>> /de...
2018 Apr 17
0
Getting glusterfs to expand volume size to brick size
...: 23.0GB
>>> Total Disk Space : 24.5GB
>>> Inode Count : 1638400
>>> Free Inodes : 1625433
>>>
>>>
>>>
>>> What's interesting here is that the gluster volume size is exactly 1/3
>>> of the total (8357M * 3 = 25071M). Yet, each block device is separate, and
>>> the total storage available is 25071M on each brick.
>>>
>>> The fstab is as follows:
>>> /dev/disk/by-id/scsi-0Linode_Volume_pylon_block1 /mnt/pylon_block1 ext4
>>> defaults 0 2
>>> /de...
2018 Apr 17
1
Getting glusterfs to expand volume size to brick size
...Total Disk Space : 24.5GB
>>>> Inode Count : 1638400
>>>> Free Inodes : 1625433
>>>>
>>>>
>>>>
>>>> What's interesting here is that the gluster volume size is exactly 1/3
>>>> of the total (8357M * 3 = 25071M). Yet, each block device is separate, and
>>>> the total storage available is 25071M on each brick.
>>>>
>>>> The fstab is as follows:
>>>> /dev/disk/by-id/scsi-0Linode_Volume_pylon_block1 /mnt/pylon_block1
>>>> ext4 defaults...
2018 Apr 17
1
Getting glusterfs to expand volume size to brick size
...Total Disk Space : 24.5GB
>>>> Inode Count : 1638400
>>>> Free Inodes : 1625433
>>>>
>>>>
>>>>
>>>> What's interesting here is that the gluster volume size is exactly 1/3
>>>> of the total (8357M * 3 = 25071M). Yet, each block device is separate, and
>>>> the total storage available is 25071M on each brick.
>>>>
>>>> The fstab is as follows:
>>>> /dev/disk/by-id/scsi-0Linode_Volume_pylon_block1 /mnt/pylon_block1
>>>> ext4 defaults...