We have found out that that up to Linux kernel 2.6.16, this problem is not appearing. However, when the Linux kernel is UPGRADED to Linux kernel 2.6.17 onwards, we seem to be hitting upon the error. This clearly indicates that the problem is arising IN BETWEEN the changes from 2.6.16 to 2.6.17 versions. Can someone please help and throw some lights what could trigger this situation? Thanks, Srini On 8/7/07, Srini <v.vvsrini@xxxxxxxxx> wrote: > Again retrying to see if some one can offer some clues here... > > Thanks in advance for your inputs, > > Srini > > ---------- Forwarded message ---------- > From: Srini <v.vvsrini@xxxxxxxxx> > Date: Aug 3, 2007 7:34 AM > Subject: Maximum number of MD devices > To: device-mapper development <dm-devel@xxxxxxxxxx> > > > Hi all, > > We are currently using Linux kernel 2.6.20-rc6 and EVMS 2.5.4 (which > internally uses device mapper) for volume management. On running the > command for creating volumes in EVMS, we find that after around 230 > volumes, EVMS starts reporting that the whole region (md/md0 for > example) has become corrupt. > > Is there a maximum limit on the number of devices that device mapper > will create that is triggering this error message? If so, are there > ways to increase the limit? > > Please let us know your inputs as it is very critical for us to > increase this limit. > > Thanks in advance, > > Srini > -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
