Re: /dev/md0 100% uso no libera espacio

15, 17:26, Camaleón <noela...@gmail.com> > escribió: > > El Fri, 30 Oct 2015 22:57:48 +0100, Maykel Franco escribió: > > > >> Buenas, tengo un pequeño dilema con mi raid5 casero con mdadm en Debian. > >> Me pone en /dev/md0 que tengo el espacio lleno: > >&

Re: /dev/md0 100% uso no libera espacio

"df -i" y "du -BM /var/lib/owncloud/data | sort -nr | less" y >>> manda el resultado. El segundo comando es lento, ten paciencia. >>> >>> >> df -i >> >> S.ficheros Nodos-i NUsados NLibres NUso% Montado en /dev/md0 >> 1

[SOLUCIONADO] Re: /dev/md0 100% uso no libera espacio

tengo un pequeño dilema con mi raid5 casero con mdadm en >> >> Debian. >> >> Me pone en /dev/md0 que tengo el espacio lleno: >> >> >> >> /dev/md0 2,7T 2,6T 0 100% /var/lib/owncloud/data >> >> >> >> Pero por

Re: /dev/md0 100% uso no libera espacio

. El segundo comando es lento, ten paciencia. >> >> > df -i > > S.ficheros Nodos-i NUsados NLibres NUso% Montado en /dev/md0 > 183123968 28473 1830954951% /var/lib/owncloud/data Pues no parece vayas corto de espacio para crear i-nodos en ese punto de montaje.

Re: /dev/md0 100% uso no libera espacio

El Wed, 04 Nov 2015 16:16:16 +0100, Maykel Franco escribió: > El día 4 de noviembre de 2015, 16:09, Camaleón > escribió: (...) >> Pues no parece vayas corto de espacio para crear i-nodos en ese punto >> de montaje. > > Si, era lo raro, he tenido que liberar 150 GB a un

Re: /dev/md0 100% uso no libera espacio

El día 31 de octubre de 2015, 17:26, Camaleón <noela...@gmail.com> escribió: > El Fri, 30 Oct 2015 22:57:48 +0100, Maykel Franco escribió: > >> Buenas, tengo un pequeño dilema con mi raid5 casero con mdadm en Debian. >> Me pone en /dev/md0 que tengo el espacio lleno: >

Re: [OT] Teléfonos móviles y listas de correo (Era: /dev/md0 100% uso no libera espacio)

Ahora seguro que sí El 31 de octubre de 2015 19:11:52 CET, Javi Barroso escribió: >Ok > >El 31 de octubre de 2015 17:30:29 CET, "Camaleón" >escribió: >>El Fri, 30 Oct 2015 22:14:23 +, Javier Barroso escribió: >> >>> Hola, perdonad el formato, el

Re: [OT] Teléfonos móviles y listas de correo (Era: /dev/md0 100% uso no libera espacio)

Ok El 31 de octubre de 2015 17:30:29 CET, "Camaleón" escribió: >El Fri, 30 Oct 2015 22:14:23 +, Javier Barroso escribió: > >> Hola, perdonad el formato, el móvil no me da para más (o sí?? Como??) > >No sé qué tipo de clientes de correo para móviles usáis algunos pero >sí,

Re: [OT] Teléfonos móviles y listas de correo (Era: /dev/md0 100% uso no libera espacio)

El Sat, 31 Oct 2015 19:11:52 +0100, Javi Barroso escribió: > Ok > > El 31 de octubre de 2015 17:30:29 CET, "Camaleón" > escribió: >>El Fri, 30 Oct 2015 22:14:23 +, Javier Barroso escribió: >> >>> Hola, perdonad el formato, el móvil no me da para más (o sí?? Como??) >>

Re: /dev/md0 100% uso no libera espacio

El Fri, 30 Oct 2015 22:57:48 +0100, Maykel Franco escribió: > Buenas, tengo un pequeño dilema con mi raid5 casero con mdadm en Debian. > Me pone en /dev/md0 que tengo el espacio lleno: > > /dev/md0 2,7T 2,6T 0 100% /var/lib/owncloud/data > > Pero por más que

[OT] Teléfonos móviles y listas de correo (Era: /dev/md0 100% uso no libera espacio)

El Fri, 30 Oct 2015 22:14:23 +, Javier Barroso escribió: > Hola, perdonad el formato, el móvil no me da para más (o sí?? Como??) No sé qué tipo de clientes de correo para móviles usáis algunos pero sí, existen aplicaciones que permiten el envío de mensajes en formato texto plano. En la

Re: /dev/md0 100% uso no libera espacio

Hola, perdonad el formato, el móvil no me da para más (o sí?? Como??) El vie., 30 oct. 2015 22:58, Maykel Franco <maykeldeb...@gmail.com> escribió: Buenas, tengo un pequeño dilema con mi raid5 casero con mdadm en Debian. Me pone en /dev/md0 que tengo el espacio lleno: /dev/md0

/dev/md0 100% uso no libera espacio

Buenas, tengo un pequeño dilema con mi raid5 casero con mdadm en Debian. Me pone en /dev/md0 que tengo el espacio lleno: /dev/md0 2,7T 2,6T 0 100% /var/lib/owncloud/data Pero por más que borro ficheros que no necesito, y bien gordos, no libera espacio... Sé que el sistema siempre

Re: /dev/md0 100% uso no libera espacio

eño dilema con mi raid5 casero con mdadm en > Debian. Me pone en /dev/md0 que tengo el espacio lleno: > > /dev/md0 2,7T 2,6T 0 100% /var/lib/owncloud/data > > Pero por más que borro ficheros que no necesito, y bien gordos, no > libera espacio... Sé que el sistem

kernel panic when doing mkfs.ext3 on a /dev/md0 (/dev/sdb /dev/sdc)

Hi, I have a fresh Debian Lenny Box with three Sata Disks (250GB and 2 X 500GB). / is mounted on the first disk (/dev/sda) outside any raid array. The other disks (/dev/sdb and /dev/sdc) have only one raid partition each and were used by mdadm to create a software raid array (/dev/md0). I keep

Re: kernel panic when doing mkfs.ext3 on a /dev/md0 (/dev/sdb /dev/sdc)

raid partition each and were used by mdadm to create a software raid array (/dev/md0). I keep getting Kernel Panic whenever I try mkfs.ext2(3|4): mkfs.ext2 /dev/md0. I googled it, but most of the kernel panic pages refers to booting from a raid array, which is not my case. TIA

Re: e2fsck /dev/md0 issues

^ The physical size of the device is 244189984 blocks ^ 24419 244189984. You need to resize your filesystem to actually fit on /dev/md0. Disk /dev/sda: 1000.2 GB, 1000204886016 bytes Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes I'm

Re: e2fsck /dev/md0 issues

On Sunday 21 December 2008, M.Lewis ca...@cajuninc.com wrote about 'Re: e2fsck /dev/md0 issues': Boyd Stephen Smith Jr. wrote: I assume that /dev/md0 knows it's size, so the filesystem superblock is bad and you should correct it by resizing the filesystem. Is there a way to know for certain

Re: e2fsck /dev/md0 issues

Boyd Stephen Smith Jr. wrote: On Sunday 21 December 2008, M.Lewis ca...@cajuninc.com wrote about 'Re: e2fsck /dev/md0 issues': Boyd Stephen Smith Jr. wrote: Maybe what I should do is break the array and start over? Making sure that e2fsck on both drives is good to go beforehand of course

Re: e2fsck /dev/md0 issues

. I'm not sure if it matters, but LVM is not installed on /dev/md0. I've tried all the possible (I think) combinations of 'e2fsck -b x /dev/md0' with no luck at all. Google searches have not yet produced anything that has seemed to help. rattler:~# e2fsck /dev/md0 e2fsck 1.41.3 (12-Oct

Re: e2fsck /dev/md0 issues

On Sun, Dec 21, 2008 at 03:44:04AM -0600, M.Lewis wrote: Boyd Stephen Smith Jr. wrote: On Sunday 21 December 2008, M.Lewis ca...@cajuninc.com wrote about 'Re: e2fsck /dev/md0 issues': Boyd Stephen Smith Jr. wrote: Maybe what I should do is break the array and start over? Making sure

Re: e2fsck /dev/md0 issues

On Sunday 2008 December 21 15:00:44 Alex Samad wrote: On Sun, Dec 21, 2008 at 03:44:04AM -0600, M.Lewis wrote: Boyd Stephen Smith Jr. wrote: On Sunday 21 December 2008, M.Lewis ca...@cajuninc.com wrote about 'Re: e2fsck /dev/md0 issues': Maybe what I should do is break the array and start

Re: e2fsck /dev/md0 issues

Boyd Stephen Smith Jr. wrote: On Sunday 2008 December 21 15:00:44 Alex Samad wrote: On Sun, Dec 21, 2008 at 03:44:04AM -0600, M.Lewis wrote: Boyd Stephen Smith Jr. wrote: On Sunday 21 December 2008, M.Lewis ca...@cajuninc.com wrote about 'Re: e2fsck /dev/md0 issues': Maybe what I should do

e2fsck /dev/md0 issues

is not installed on /dev/md0. I've tried all the possible (I think) combinations of 'e2fsck -b x /dev/md0' with no luck at all. Google searches have not yet produced anything that has seemed to help. rattler:~# e2fsck /dev/md0 e2fsck 1.41.3 (12-Oct-2008) The filesystem size (according to the superblock

Re: e2fsck /dev/md0 issues

^ 24419 244189984. You need to resize your filesystem to actually fit on /dev/md0. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net

Re: e2fsck /dev/md0 issues

^ 24419 244189984. You need to resize your filesystem to actually fit on /dev/md0. Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x6c53e0bd Device

Re: e2fsck /dev/md0 issues

size of the device is 244189984 blocks ^ 24419 244189984. You need to resize your filesystem to actually fit on /dev/md0. Disk /dev/sda: 1000.2 GB, 1000204886016 bytes Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes I'm confused. It's

Re: Fail event on /dev/md0:phreaque

Christofer C. Bell [EMAIL PROTECTED]: On Fri, Jun 20, 2008 at 10:45 PM, s. keeling [EMAIL PROTECTED] wrote: Hi. I've been fiddling with a RAID5 on usb pendrives plugged into usb Your system has a raid5 array configured as /dev/md0 containing disks sda, sdb, and sdc. Your sdb disk has

Re: Fail event on /dev/md0:phreaque

as /dev/md0 containing disks sda, sdb, and sdc. Your sdb disk has failed. This is pretty explicitly stated in the error message: A Fail event had been detected on md device /dev/md0. It could be related to component device /dev/sdb1. -- Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED

Fwd: Fail event on /dev/md0:phreaque

] - Received: from root by phreaque.nucleus.com with local (Exim 4.63) (envelope-from [EMAIL PROTECTED]) id 1K9tal-0005Oz-8B for [EMAIL PROTECTED]; Fri, 20 Jun 2008 21:16:43 -0600 From: mdadm monitoring [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Fail event on /dev/md0

Re: using UUID's for a raid1 in /etc/fstab instead of /dev/md0

On Thu, Apr 10, 2008 at 01:35:03AM -0400, Mitchell Laks wrote: Thank you all for this very informative thread. So it seems that running blkid is the answer insofar as it tells me the information I need. I wonder: does this also work for lvm managed partitions? ?? this is an excerpt

Re: using UUID's for a raid1 in /etc/fstab instead of /dev/md0

also sprach Mitchell Laks [EMAIL PROTECTED] [2008.04.09.0508 +0200]: Someone recently talked about using ls -l /dev/disk/by-uuid to figure out the correct UUID to put into /etc/fstab for hard drives. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435983 -- .''`. martin f. krafft

Re: using UUID's for a raid1 in /etc/fstab instead of /dev/md0

On Tue, Apr 08, 2008 at 11:08:11PM -0400, Mitchell Laks wrote: Hi, Someone recently talked about using ls -l /dev/disk/by-uuid to figure out the correct UUID to put into /etc/fstab for hard drives. I have /home on a raid1 /dev/md0 which is composed of two drive partitions /dev/sda1

Re: using UUID's for a raid1 in /etc/fstab instead of /dev/md0

Alex Samad wrote: On Tue, Apr 08, 2008 at 11:08:11PM -0400, Mitchell Laks wrote: Hi, Someone recently talked about using ls -l /dev/disk/by-uuid to figure out the correct UUID to put into /etc/fstab for hard drives. I have /home on a raid1 /dev/md0 which is composed of two drive

Re: using UUID's for a raid1 in /etc/fstab instead of /dev/md0

On Wed, Apr 09, 2008 at 10:27:43AM -0400, Damon L. Chesser wrote: Alex Samad wrote: On Tue, Apr 08, 2008 at 11:08:11PM -0400, Mitchell Laks wrote: Hi, [snip] I looked at tune2fs -l /dev/md0: Filesystem UUID: d3bb5b79-2d5f-438d-a60e-5437e80e2edf from ls -l /dev/disk/by-uuid

Re: using UUID's for a raid1 in /etc/fstab instead of /dev/md0

=ext2 TYPE=ext3 so if i wanted to mount my / partition (/dev/md0 is /boot), then I could put UUID=ec3e3537-4e36-443e-8132-5b0f03dd0978 / auto .. in my fstab file Alex Alex, I think you have it, though I can't explain the different UUIDs from tune2fs and mdadm --detail. I would rather put

Re: using UUID's for a raid1 in /etc/fstab instead of /dev/md0

md1 /dev/md1: LABEL=/ UUID=ec3e3537-4e36-443e-8132-5b0f03dd0978 SEC_TYPE=ext2 TYPE=ext3 so if i wanted to mount my / partition (/dev/md0 is /boot), then I could put UUID=ec3e3537-4e36-443e-8132-5b0f03dd0978 / auto .. in my fstab file Alex Alex, I think you have it, though I

Re: using UUID's for a raid1 in /etc/fstab instead of /dev/md0

Thank you all for this very informative thread. So it seems that running blkid is the answer insofar as it tells me the information I need. I wonder: does this also work for lvm managed partitions? (an idea that seemed to be vetted but not concluded by the above thread posters.) Mitchell

using UUID's for a raid1 in /etc/fstab instead of /dev/md0

Hi, Someone recently talked about using ls -l /dev/disk/by-uuid to figure out the correct UUID to put into /etc/fstab for hard drives. I have /home on a raid1 /dev/md0 which is composed of two drive partitions /dev/sda1 /dev/sdb1 Now in /etc/mdadm/mdadm.conf I have: ARRAY /dev/md0 level

Re: using UUID's for a raid1 in /etc/fstab instead of /dev/md0

for raid members irrespective of /dev name when it reassembles the raid on boot. /dev/md0 will always be /dev/md0 and not /dev/md3 or something. FYI, LVM is the same way, only its /dev/mapper... Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble

Re: using UUID's for a raid1 in /etc/fstab instead of /dev/md0

On Tue, Apr 08, 2008 at 11:08:11PM -0400, Mitchell Laks wrote: ls -l /dev/disk/by-uuid So that must be the UUID for the individual /dev/sda1 and /dev/sdb1. What is the UUID for the raid1 itself? Perhaps blkid might help (at lest it works for me, and my machines do NON use udev and do NOT have

Re: using UUID's for a raid1 in /etc/fstab instead of /dev/md0

itself? Doesn't matter. The raid subsystem will search all disks for raid members irrespective of /dev name when it reassembles the raid on boot. /dev/md0 will always be /dev/md0 and not /dev/md3 or something. FYI, LVM is the same way, only its /dev/mapper... Doug. Hey, The raid subsystem

Re: DegradedArray event on /dev/md0:debian

sdb1 est la partie 0/1 du raid qui fonctionne tenter: mdadm /dev/md0 -r /dev/hdoupartitionHS -a /dev/hdoupartitionHS sinon: mount /dev/md0 /ouskejlemonte -o remount,ro e2fsck /dev/md0 si malgré tout ça plante à la reconstruction, ça veut dire que le HD|partition a un PB hardware et qu'il vaut

DegradedArray event on /dev/md0:debian

 : DegradedArray event on /dev/md0:debian This is an automatically generated mail message from mdadm running on debian A DegradedArray event had been detected on md device /dev/md0. Faithfully yours, etc. P.S. The /proc/mdstat file currently contains the following: Personalities : [raid1] md0 : active

Arrancar /dev/md0 en knoppix

Necesito levantar un raid instalado en mi servidor desde una knoppix (perdió la original su fstab por error manual) Intentándolo montar no ha habido forma de que me lo hiciera Miré por aquí http://hup.hu/node/33250 e intenté hacerle un mdadm --create /dev/md0 --level=1 --raid-devices=2

Re: Arrancar /dev/md0 en knoppix

/dev/md0 --level=1 --raid-devices=2 /dev/sda3 /dev/sdb3 y el error es el siguiente mdadm: error opening /dev/md0: No such device or address Estuve mirando y parece que va por el udev de la knoppix, el caso que filtreando por la red no encuentro información de ayuda para levantar un raid desde

[Fwd: Re: Arrancar /dev/md0 en knoppix]

datos y en sistema No mantener el raid En conclusión / fuera del raid /datos en raid. /boot /dev/sda1 en ext3 / /dev/sda3 en xfs swap /dev/sda2 /dev/sda4 VOLUMEN FISICO RAID /boot /dev/sdb1 en ext3 /opt /dev/sdb3 en xfs swap /dev/sdb2 /dev/sdb4 VOLUMEN FISICO RAID Luego en /dev/md0 /datos xfs Así

Re: Arrancar /dev/md0 en knoppix

intenté hacerle un mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sda3 /dev/sdb3 y el error es el siguiente mdadm: error opening /dev/md0: No such device or address Estuve mirando y parece que va por el udev de la knoppix, el caso que filtreando por la red no encuentro información de

Re: Criar dispositivo /dev/md0 para Raid [RESOLVIDO]

Cara, No meu caso o RAID fica em Hds separados do boot, deste jeito que vc falou ai eu nunca fiz não. http://www.freesoftwarebrasil.com.br/content/view/197/56/ dá uma olhada no material acima deve dar uma luz... vc usa o software mdadm para ativar o raid. Qualquer dúvida me avise Pedro

Criar dispositivo /dev/md0 para Raid

Olá Pessoal, Estou montando um novo servidor que vai usar RAID1 via software. Estou usando o kernel 2.6.19.2 para poder usar o sistema com HD SATA. Porém qdo dou boot com este kernel ele não mostra os dispositivos mdx dentro do /dev, e vou precisar deles para poder montar o RAID. Eu sei que

Re: Criar dispositivo /dev/md0 para Raid - DUVIDA

Olá, Muito bons os artigos, mas antes eu preciso saber como habilitar este dispositivo /dev/md0 dentro do kernel, pois ele não aparece para eu poder continuar com a criação do raid. Obrigado Pedro Bruno Criado escreveu: Veja se pode ajudar: http://www.vivaolinux.com.br/artigos

Re: Criar dispositivo /dev/md0 para Raid

precisar deles para poder montar o RAID. Tentou criar com o mdadm? # mdadm -C /dev/md0 --level=raid1 --raid-devices=2 /dev/sda1 /dev/sdb1 -C cria o dispositivo , --levle é o nível do raid (no teu caso raid1) e raid devices tem o número de dispositivos seguido do caminho para os dispositivos que

Re: Criar dispositivo /dev/md0 para Raid [RESOLVIDO]

servidor que vai usar RAID1 via software. Estou usando o kernel 2.6.19.2 para poder usar o sistema com HD SATA. Porém qdo dou boot com este kernel ele não mostra os dispositivos mdx dentro do /dev, e vou precisar deles para poder montar o RAID. Tentou criar com o mdadm? # mdadm -C /dev/md0

Re: /dev/md0 don't start after controller change

On 12/11/06, michael [EMAIL PROTECTED] wrote: Perhaps partitions from sdd and sde need to be re-added as well? Surely I must add sdd, sde and sdf, but my problem is another: If I add those partitions (sdc included) after reboot /dev/md0 lost information about them, and it shows raid schema

Re: /dev/md0 don't start after controller change

On Tue, 2006-12-12 at 09:33 +0100, Andrea Ganduglia wrote: Surely I must add sdd, sde and sdf, but my problem is another: If I add those partitions (sdc included) after reboot /dev/md0 lost information about them, and it shows raid schema with two working disks and three set as removed. I

Re: /dev/md0 don't start after controller change

also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.07.1225 +0100]: Surely I must add sdd, sde and sdf, but my problem is another: If I add those partitions (sdc included) after reboot /dev/md0 lost information about them, and it shows raid schema with two working disks and three set

Re: /dev/md0 don't start after controller change

On 12/12/06, martin f krafft [EMAIL PROTECTED] wrote: also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.07.1225 +0100]: Surely I must add sdd, sde and sdf, but my problem is another: If I add those partitions (sdc included) after reboot /dev/md0 lost information about them, and it shows

Re: /dev/md0 don't start after controller change

also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.12.1231 +0100]: Are you sure? I think that the problem do not depend by sd{c,d,e,f} but by sd{a,b}. Please: look mdadm -E output from previous messages. I am not sure what the problem is. Thus I am trying to work through various possibly

Re: /dev/md0 don't start after controller change

On Mon, 11 Dec 2006 08:56:39 +0100, Andrea Ganduglia wrote pro:~# mdadm --detail --scan ARRAY /dev/md1 level=raid5 num-devices=5 spares=1 UUID=04a39ca8:0f07922a:5eb2e3a1:851b13b9 devices=/dev/sda2,/dev/sdf2,/dev/sdd2,/dev/sdc2,/dev/sde2, /dev/sdb2 ARRAY /dev/md0 level=raid1 num-devices

Re: /dev/md0 don't start after controller change

? There are important differences pro:~# mdadm --add /dev/md0 /dev/sdc1 pro:~# cat /etc/mdadm/mdadm.conf DEVICE partitions ARRAY /dev/md1 level=raid5 num-devices=5 spares=1 UUID=04a39ca8:0f07922a:5eb2e3a1:851b13b9 devices=/dev/sda2,/dev/sdb2,/dev/sdc2,/dev/sdd2,/dev/sde2,/dev/sdf2 ARRAY /dev

Re: /dev/md0 don't start after controller change

also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.05.1557 +0400]: But if I do this command onto RAID1 it said that md0 is still in use (sure! is root's partition!). If I add manually others disk (mdadm --add /dev/md0 /dev/sdc1) it works, but on reboot only sda1 and sdb1 are parts

Re: /dev/md0 don't start after controller change

On 12/7/06, martin f krafft [EMAIL PROTECTED] wrote: also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.05.1557 +0400]: But if I do this command onto RAID1 it said that md0 is still in use (sure! is root's partition!). If I add manually others disk (mdadm --add /dev/md0 /dev/sdc1

Re: /dev/md0 don't start after controller change

also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.07.1249 +0400]: md0 : active raid1 sda1[0] sdb1[1] 29294400 blocks [5/2] [UU___] I am led to believe that there must be some outdated information in the superblocks. Can you please post the output of mdadm -E /dev/sd[acde]1 , or

Re: /dev/md0 don't start after controller change

divergencies. As you see /dev/sd{c,d,e,f}1 look all active devices on /dev/md0, instead /dev/sd{a,b}1 look only two devices at same raid. Summary: /dev/sd{a,b}1 looks 2 working devices and 3 failed devices /dev/sd{c,d,e}1 looks 5 working devices and 0 failed devices /dev/sdf1 looks 5 working devices

Re: /dev/md0 don't start after controller change

also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.07.1432 +0400]: How can I fix superblocks informations? Consider that /dev/md0 is mounted on root partitions (/). mdadm --add /dev/md0 /dev/sd[cde]1 should work. Your components got bumped from the array after they were marked failed

Re: /dev/md0 don't start after controller change

On 12/7/06, martin f krafft [EMAIL PROTECTED] wrote: also sprach Andrea Ganduglia [EMAIL PROTECTED] [2006.12.07.1432 +0400]: How can I fix superblocks informations? Consider that /dev/md0 is mounted on root partitions (/). mdadm --add /dev/md0 /dev/sd[cde]1 should work. Your components got

Re: /dev/md0 don't start after controller change

On Thu, 7 Dec 2006 12:25:40 +0100, Andrea Ganduglia wrote In some way /dev/sda1 and /dev/sdb1 lost information about --add option after any reboot. :-( After you add your partition, how does mdadm --detail --scan compare to /etc/mdadm/mdadm.conf ? Mike -- To UNSUBSCRIBE, email to [EMAIL

/dev/md0 don't start after controller change

controller, and leave from /etc/fstab RAID5 references (preserving data). Now, I have change PCI SATA controller and it works perfetly, but /dev/md0 (RAID1) do not start correctly. For resync and active RAID5 I done: ~# mdadm --assemble --scan /dev/md1 But if I do this command onto RAID1 it said

zmiany na /dev/md0

Hello debian-user-polish, Przekopalem cala mase stron o tym i udalo mi sie znalezc to czego szukam - czyli jak zamienic dysk spare na dysk w mirrorze. No ale jest ale. md0 to / i tu jet problem operacje na macierzy wykonuje sie po zatrzymaniu macierzy. wiec startuje knoppixa z

Re: zmiany na /dev/md0

Dnia 15-08-2006, wto o godzinie 22:28 +0200, Artur Homeniuk napisał(a): Hello debian-user-polish, Przekopalem cala mase stron o tym i udalo mi sie znalezc to czego szukam - czyli jak zamienic dysk spare na dysk w mirrorze. No ale jest ale. md0 to / i tu jet problem operacje na

Re: Não tenho o /dev/md0

Use o comando mkdev Abraço. Pedro - Debian wrote: Olá pessoal Estou colocando implantando um sistema com RAID 1, em um servidor Debian 3. Meu kernel é o 2.6..8-3-686, e o danado não tem o dispositivo /dev/mdx, como faço para poder criar ele... Imagino que seja algo no kernel mas não

Re: Não tenho o /dev/md0

Em 27/07/06, Pedro - Debian[EMAIL PROTECTED] escreveu: Olá pessoal Estou colocando implantando um sistema com RAID 1, em um servidor Debian 3. Meu kernel é o 2.6..8-3-686, e o danado não tem o dispositivo /dev/mdx, como faço para poder criar ele... Imagino que seja algo no kernel mas não

Re: Não tenho o /dev/md0

Sent: Thursday, July 27, 2006 8:38 PM Subject: Não tenho o /dev/md0 Olá pessoal Estou colocando implantando um sistema com RAID 1, em um servidor Debian 3. Meu kernel é o 2.6..8-3-686, e o danado não tem o dispositivo /dev/mdx, como faço para poder criar ele... Imagino que seja algo

Não tenho o /dev/md0

Olá pessoal Estou colocando implantando um sistema com RAID 1, em um servidor Debian 3. Meu kernel é o 2.6..8-3-686, e o danado não tem o dispositivo /dev/mdx, como faço para poder criar ele... Imagino que seja algo no kernel mas não sei... Desde já agradeço... Obrigado Pedro -- To

Re: mdadm --create /dev/md0 ... - error ...: No such file

Hallo Daniel, Daniel Musketa schrieb: Hallo, b) Um nicht später nochmal neu zu fragen: Wo legt mdadm die Informationen über die zu benutzenden RAIDs ab, d. h. wie portabel ist so ein RAID-Verbund? Die Informationen zum Raid werden auf den Platten selbst abgelegt (Stichworte superblock und

Re: mdadm --create /dev/md0 ... - error ...: No such file

* Daniel Musketa: # lsmod | egrep md|raid; ls -ld /dev/md* raid1 17536 0 md 49544 1 raid1 ls: /dev/md*: Datei oder Verzeichnis nicht gefunden Meine Erinnerung trog mich leider, Du hast recht: Nur vom Laden der Moduln gibts noch keine

Position Superblock bei mdadm [war: mdadm --create /dev/md0 ... - error ...: No such file]

Am Sonntag 28 Mai 2006 10:46 schrieb Thorsten Strusch: Daniel Musketa schrieb: b) Um nicht später nochmal neu zu fragen: Wo legt mdadm die Informationen über die zu benutzenden RAIDs ab, d. h. wie portabel ist so ein RAID-Verbund? Die Informationen zum Raid werden auf den Platten selbst

Gelöst: mdadm --auto [war: mdadm --create /dev/md0 ... - error ...: No such file]

Gleichheitszeichen nach der Level-Angabe. # fdisk -l /dev/hda | fgrep hda4 /dev/hda4 11213 1945766227962+ fd Linux raid autodetect # modprobe md # modprobe raid1 # cat /proc/mdstat Personalities : [raid1] unused devices: none # mdadm --create /dev/md0 --level=1 --raid-devices=2

Re: Position Superblock bei mdadm [war: mdadm --create /dev/md0 ... - error ...: No such file]

Daniel Musketa schrieb: Am Sonntag 28 Mai 2006 10:46 schrieb Thorsten Strusch: Daniel Musketa schrieb: b) Um nicht später nochmal neu zu fragen: Wo legt mdadm die Informationen über die zu benutzenden RAIDs ab, d. h. wie portabel ist so ein RAID-Verbund? Die Informationen zum Raid werden auf

Re: Gelöst: mdadm --auto [war: mdadm --create /dev/md0 ... - error ...: No such file]

* Daniel Musketa: Und da war's: -a man mdadm: -a, --auto{=no,yes,md,mdp,part,p}{NN} Instruct mdadm to create the device file if needed ... Damit ging's dann. Das Device wurde beim Aufruf von mdadm erstellt. Jetzt habe ich auch den zugehörigen Hinweis gefunden: Unter

mdadm --create /dev/md0 ... - error ...: No such file

Hallo, ich wollte gerade auf Debian Sarge ein RAID einrichten. Dafür habe ich mdadm installiert. Versuche ich jetzt, mittels mdadm --create /dev/md0 --level 1 ... das RAID anzulegen, erhalte ich die Meldung mdadm: error opening /dev/md0: No such file or directory Und Recht hat es: Es

Re: mdadm --create /dev/md0 ... - error ...: No such file

* Daniel Musketa: ich wollte gerade auf Debian Sarge ein RAID einrichten. Dafür habe ich mdadm installiert. Versuche ich jetzt, mittels mdadm --create /dev/md0 --level 1 ... das RAID anzulegen, erhalte ich die Meldung mdadm: error opening /dev/md0: No such file or directory

Re: /dev/md0 and udev

Richard Weil [EMAIL PROTECTED] writes: Sorry to be stupid, put I can't find much documentation on the udev/links.conf file. Would I add the following to links.conf in order to create /dev/md0? M md0b 9 0 Probably M md I'm not sure of the distinction between L, D, M in the file

Re: /dev/md0 and udev

Antonio Rodriguez [EMAIL PROTECTED] writes: Whats the udev email list location? Is there any irc channel for udev, by udev developers, or experts? http://linux-hotplug.sourceforge.net (I know it says hotplug, but udev seems to share it with hotplug for this list). I really don't know any IRC

Re: /dev/md0 and udev

Richard Weil [EMAIL PROTECTED] writes: I'm running Sarge with a 2.6.5 kernel. I'm trying to create a RAID 5 array of three disks (though for initial setup I'm only using two of three). When I reboot, udev does not re-create my /dev/md0 device, so the RAID array won't start. Any suggestions

Re: /dev/md0 and udev

-create my /dev/md0 device, so the RAID array won't start. Any suggestions? udev won't create the md? devices because the RAID never notifies udev/sysfs about it. The just have a thread about on the udev mailing list. You need to create the md? devices manually by putting it in the /etc/udev

Re: /dev/md0 and udev

Sorry to be stupid, put I can't find much documentation on the udev/links.conf file. Would I add the following to links.conf in order to create /dev/md0? M md0b 9 0 I'm not sure of the distinction between L, D, M in the file, though I assume L is link, D is directory and M is some sort

/dev/md0 and udev

I'm running Sarge with a 2.6.5 kernel. I'm trying to create a RAID 5 array of three disks (though for initial setup I'm only using two of three). When I reboot, udev does not re-create my /dev/md0 device, so the RAID array won't start. Any suggestions? I found a posting online saying that udev

Re: Raid; mkraid /dev/md0

Frans == Frans Schreuder [EMAIL PROTECTED] writes: Frans Thanx for the reply. FYI: the raidtab file is /etc/raidtab (and Frans also /etc/raid/raidtab) The raidtab looks OK to me. What are the partitions on your disks? -- G. ``Iggy'' Geens - ICQ: #64109250 Home: [EMAIL PROTECTED] - Work:

Re: Raid; mkraid /dev/md0

Message - From: Guy Geens [EMAIL PROTECTED] To: debian-user@lists.debian.org Sent: Sunday, June 17, 2001 8:58 AM Subject: Re: Raid; mkraid /dev/md0 Frans == Frans Schreuder [EMAIL PROTECTED] writes: Frans Thanx for the reply. FYI: the raidtab file is /etc/raidtab (and Frans also /etc/raid

Re: Raid; mkraid /dev/md0

Frans == Frans Schreuder [EMAIL PROTECTED] writes: Frans Primary partition only one; fd filetype (linux raid auto). For Frans each disk.(hdb; hdc).They are identical disks but Frans clusters/heads/sectors differ?? The CHS figures shouldn't matter, as long as fdisk reports the same size for

Re: Raid; mkraid /dev/md0

Thanx for the reply. FYI: the raidtab file is /etc/raidtab (and also /etc/raid/raidtab) Raidtab: raiddev /dev/md0 raid-level0 nr-raid-disks2 persistent-superblock1 chunk-size8 device/dev/hdb1 raid-disk0 device

Re: Raid; mkraid /dev/md0

Frans == Frans Schreuder [EMAIL PROTECTED] writes: Frans I've attached the original message if anyone can shine a light Frans on this thing that will not work. It's really the mkraid Frans /dev/md0 part that won't work. Did you try after you copied the raidtab to the correct place? Can you

Fw: Raid; mkraid /dev/md0

in the package.) Hence the copy I thought that it maybe could be used for a mount-point but isn't it a bit silly to have it in etc? I've attached the original message if anyone can shine a light on this thing that will not work. It's really the mkraid /dev/md0 part that won't work. Thanx anyway

Re: Raid; mkraid /dev/md0

Frans == Frans Schreuder [EMAIL PROTECTED] writes: Frans -edited the raidtab file ( I noticed there beeing a raid Frans directory so I copied it from it's original location in /etc) The raidtab file needs to be in /etc. I have noticed the /etc/raid directory as well, but AFAIK it is not used.

Raid; mkraid /dev/md0

Hai all I've been wanting to play with raid. Reading the software-raid-howto; I stranded on mkraid /dev/md0 That darn thing did not want to. -apt-got raidtools2 dpkg-i kernelpatch...2.2.10.. -edited the raidtab file ( I noticed there beeing a raid directory so I copied it from it's

Re: /dev/md0

On Thu, 09 Oct 1997 14:26:02 +0200 Pere Camps ([EMAIL PROTECTED]) wrote: I have a linear partition on my linux box (/dev/md0 = hdb7+hdb9+hdb11), and when I run the `mdadd -ar`, and I then mount the filesystem something like the following comes up: Warning: /dev/md0 has

Re: /dev/md0

Phil, This is because you created you mdtab by hand, and not with mdcreate. Mdcreate computes a checksum and puts it in the mdtab. When mdrunning a md partition, the checksum is computed and is compared to the one stored in the mdtab. If they're different, the md device isn't started.

/dev/md0

Hi, I have a linear partition on my linux box (/dev/md0 = hdb7+hdb9+hdb11), and when I run the `mdadd -ar`, and I then mount the filesystem something like the following comes up: Warning: /dev/md0 has no checksum field Should I worry? Salutacions, Pere