Hi devs, list! I've got somewhat simple but in same time pretty difficult question. But I'm running glusterf in production and don't have any option to test myself :( say I've got a distributed gluster volume of 2x350GB I want to export ISCSI target for M$ server and I want it to be 600GB. I understand, that when I create a large file for ISCSI target with dd, it will be distributed between two bricks. And here comes the question: What will happen when 1. one of bricks goes down? Ok, simple - target won't be accessible. 2. would be data available again, when the brick comes back up? (ie failure due to network or power) yes, we have backup server and ups and generator, as we are running DC, but I'm just curious if we will have to restore the data from backups or it will be available after brick comes back up? -- Best regards, Roman. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150401/7367d25e/attachment.html>
Well, I meant stripe volume :) As file size should exceed brick's size. And questions remain the same. Hope for a quick response. 2015-04-01 11:38 GMT+03:00 Roman <romeo.r at gmail.com>:> Hi devs, list! > > I've got somewhat simple but in same time pretty difficult question. But > I'm running glusterf in production and don't have any option to test myself > :( > > say I've got a distributed gluster volume of 2x350GB > I want to export ISCSI target for M$ server and I want it to be 600GB. > I understand, that when I create a large file for ISCSI target with dd, it > will be distributed between two bricks. And here comes the question: > > What will happen when > > 1. one of bricks goes down? Ok, simple - target won't be accessible. > 2. would be data available again, when the brick comes back up? (ie > failure due to network or power) > > yes, we have backup server and ups and generator, as we are running DC, > but I'm just curious if we will have to restore the data from backups or it > will be available after brick comes back up? > > > > -- > Best regards, > Roman. >-- Best regards, Roman. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150401/14400b99/attachment.html>
----- Original Message -----> From: "Roman" <romeo.r at gmail.com> > To: gluster-users at gluster.org > Sent: Wednesday, April 1, 2015 4:38:50 AM > Subject: [Gluster-users] iscsi and distributed volume > > Hi devs, list! > > I've got somewhat simple but in same time pretty difficult question. But I'm > running glusterf in production and don't have any option to test myself :( > > say I've got a distributed gluster volume of 2x350GB > I want to export ISCSI target for M$ server and I want it to be 600GB. > I understand, that when I create a large file for ISCSI target with dd, it > will be distributed between two bricks. And here comes the question: > > What will happen when > > 1. one of bricks goes down? Ok, simple - target won't be accessible. > 2. would be data available again, when the brick comes back up? (ie failure > due to network or power) > > yes, we have backup server and ups and generator, as we are running DC, but > I'm just curious if we will have to restore the data from backups or it will > be available after brick comes back up?What kind of gluster volume is it- I would hope it is replicated? Data within the file is not distributed between two bricks, unless your volume type is striped. Assuming its replicated, if one brick went down, the other replica would continue to operate, so you would have availability.> > > > -- > Best regards, > Roman. > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://www.gluster.org/mailman/listinfo/gluster-users