Displaying 3 results from an estimated 3 matches for "1742m".
Did you mean:
1742
2018 Apr 17
1
Getting glusterfs to expand volume size to brick size
..._block1
/dev/sdc 26079M
1491M 23241M 7% /mnt/pylon_block2
/dev/sde 25071M
1491M 22315M 7% /mnt/pylon_block3
localhost:/dev_apkmirror_data 25071M
1742M 22284M 8% /mnt/dev_apkmirror_data1
localhost:/dev_apkmirror_data 25071M
1742M 22284M 8% /mnt/dev_apkmirror_data2
localhost:/dev_apkmirror_data 25071M
1742M 22284M 8% /mnt/dev_apkmirror_data3
localhost:/dev_apkmirror_...
2018 Apr 17
0
Getting glusterfs to expand volume size to brick size
Ok, it looks like the same problem.
@Amar, this fix is supposed to be in 4.0.1. Is it possible to regenerate
the volfiles to fix this?
Regards,
Nithya
On 17 April 2018 at 09:57, Artem Russakovskii <archon810 at gmail.com> wrote:
> pylon:/var/lib/glusterd/vols/dev_apkmirror_data # ack shared-brick-count
> dev_apkmirror_data.pylon.mnt-pylon_block3-dev_apkmirror_data.vol
> 3:
2018 Apr 17
5
Getting glusterfs to expand volume size to brick size
pylon:/var/lib/glusterd/vols/dev_apkmirror_data # ack shared-brick-count
dev_apkmirror_data.pylon.mnt-pylon_block3-dev_apkmirror_data.vol
3: option shared-brick-count 3
dev_apkmirror_data.pylon.mnt-pylon_block2-dev_apkmirror_data.vol
3: option shared-brick-count 3
dev_apkmirror_data.pylon.mnt-pylon_block1-dev_apkmirror_data.vol
3: option shared-brick-count 3
Sincerely,
Artem
--