search for: 25071m

Displaying 9 results from an estimated 9 matches for "25071m".

Getting glusterfs to expand volume size to brick size
2018 Apr 17
1
Getting glusterfs to expand volume size to brick size
...: option shared-brick-count 1 dev_apkmirror_data.pylon.mnt-pylon_block2-dev_apkmirror_data.vol 3: option shared-brick-count 1 dev_apkmirror_data.pylon.mnt-pylon_block1-dev_apkmirror_data.vol 3: option shared-brick-count 1 /dev/sdd 25071M 1491M 22284M 7% /mnt/pylon_block1 /dev/sdc 26079M 1491M 23241M 7% /mnt/pylon_block2 /dev/sde 25071M 1491M 22315M 7% /mnt/pylon_block3 localhost:/dev_apkmirror_data...
Getting glusterfs to expand volume size to brick size
2018 Apr 17
0
Getting glusterfs to expand volume size to brick size
...GB >>> 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/...
Getting glusterfs to expand volume size to brick size
2018 Apr 17
5
Getting glusterfs to expand volume size to brick size
...> 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_pylo...
Getting glusterfs to expand volume size to brick size
2018 Apr 16
2
Getting glusterfs to expand volume size to brick size
...ount 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 0 2 /dev/dis...
Getting glusterfs to expand volume size to brick size
2018 Apr 14
2
Getting glusterfs to expand volume size to brick size
...ilable space and extend to use it. Multiple Google searches, and I'm still nowhere. Any ideas? df | ack "block|data" Filesystem 1M-blocks Used Available Use% Mounted on /dev/sdd 25071M 1491M 22284M 7% /mnt/pylon_block1 /dev/sdc 26079M 1491M 23241M 7% /mnt/pylon_block2 /dev/sde 25071M 1491M 22315M 7% /mnt/pylon_block3 localhost:/dev_apkmirror_data...
Getting glusterfs to expand volume size to brick size
2018 Apr 17
0
Getting glusterfs to expand volume size to brick size
...> 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_bloc...
Getting glusterfs to expand volume size to brick size
2018 Apr 16
0
Getting glusterfs to expand volume size to brick size
.... > > Multiple Google searches, and I'm still nowhere. Any ideas? > > df | ack "block|data" > Filesystem 1M-blocks > Used Available Use% Mounted on > /dev/sdd 25071M > 1491M 22284M 7% /mnt/pylon_block1 > /dev/sdc 26079M > 1491M 23241M 7% /mnt/pylon_block2 > /dev/sde 25071M > 1491M 22315M 7% /mnt/pylon_block3 > localhost:...
Getting glusterfs to expand volume size to brick size
2018 Apr 17
0
Getting glusterfs to expand volume size to brick size
...GB >>> 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/...
Getting glusterfs to expand volume size to brick size
2018 Apr 17
1
Getting glusterfs to expand volume size to brick size
...pace : 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 >>&...