Re: e2fsck detail check

Thanks much, highly informative. On Sun, 30 Dec 2018, David wrote: > Date: Sat, 29 Dec 2018 18:18:41 > From: David > To: debian-user > Subject: Re: e2fsck detail check > Resent-Date: Sat, 29 Dec 2018 23:19:07 + (UTC) > Resent-From: debian-user@lists.debian.org > > O

Re: e2fsck detail check

l you use to start e2fsck interactively, or the shell script that starts e2fsck. You can read about file descriptors here: http://mywiki.wooledge.org/FileDescriptor The e2fsck man page also explains that if you precede the fd number with a minus sign, then e2fsck will defer writing to the file d

Re: e2fsck detail check

On 12/29/18 7:20 PM, Jude DaShiell wrote: I have a question about the -c fd command line switch. Would the valid options for fd be stdin stdout and stderr? I may need to provide remote support for someone and it will be helpful if e2fsck can show completion percentage as any repair happens. I

e2fsck detail check

I have a question about the -c fd command line switch. Would the valid options for fd be stdin stdout and stderr? I may need to provide remote support for someone and it will be helpful if e2fsck can show completion percentage as any repair happens. --

Re: e2fsck automatique au boot

Bonjour. Merci à vous tous. J'ai trouvé ma/mes solutions. L'option «defaults» résout le problème. L'utilitaire tune2fs me donne plein d'infos et de paramétrages possibles. Bien sur, fsck.xxx, est de la partie. Merci encore à tous ! À bientôt. Le Tue, 13 Jun 2017 09:35:47 +0200, Haricophile

Re: e2fsck automatique au boot

Le Tue, 13 Jun 2017 06:43:33 +0200, "Pierre L." a écrit : > J'ai souvenir qu'il existait une commande (à l'époque Ubuntesque...) > pour connaître le nombre de reboots restants avant un scan auto... à > voir si ca fonctionne encore ! tune2fs (installer e2tools je crois)

Re: e2fsck automatique au boot

Salut, Il me semble effectivement que le disque a besoin d'être automatiquement monté via fstab au boot pour qu'il soit automatiquement "scanné" par e2fsck. Si tu le montes à la main, le système ne devrait logiquement pas y avoir accès, et ca râle ? Ca peut valoir le coup de voir ce qu

Re: e2fsck automatique au boot

Bonjour. Ah forcément il fallait que j'oublie quelque chose dans ma description... Alors effectivement ce disque apparaît dans le fstab. UUID="d845-2f8x-40xx-88xx-630b4891819" /mnt/Ledisqueext3 rw,users,noauto 0 2 Mais je le monte uniquement «à la main» quand nécessaire

Re: e2fsck automatique au boot

Bonsoir C'est un disque monté avec fstab ? - Mail original - De: "list" <l...@contacte.xyz> À: debian-user-french@lists.debian.org Envoyé: Dimanche 11 Juin 2017 00:44:51 Objet: e2fsck automatique au boot Salut la liste. Debian 8.7 En regardant les logs je tombe sur un

e2fsck automatique au boot

Salut la liste. Debian 8.7 En regardant les logs je tombe sur un : kernel: EXT4-fs (sdc7): warning: maximal mount count reached, running e2fsck is recommended Un petit : systemctl status systemd-fsck@dev-disk-by\x2duuid-d845dba2\x2d2f87\x2d40b7\x2d881c\x2d630f47931810.service me donne

Re: Les mystères de tune2fs et de e2fsck

ut-être que le scan soit lancé ? As-tu essayé de lancer manuellement e2fsck ? Est-ce que ces dates sont cohérentes ensuite ? Sébastien

Re: Les mystères de tune2fs et de e2fsck

heck after: Fri Nov 27 20:38:41 2015 * > > Ces deux dates sont loin dans le passé (plus d'un mois) ça expliquerait > peut-être que le scan soit lancé ? > > As-tu essayé de lancer manuellement e2fsck ? Est-ce que ces dates sont > cohérentes ensuite ? > > Sébastie

Les mystères de tune2fs et de e2fsck

Bonjour, Mon système est une Debian Sid AMD64, suite au fait que la debian Sid Kde est en période d'instabilité obligeant de redémarrer le système plusieurs fois par jour pour pouvoir travailler, j'ai modifié avec l'aide de tune2fs la périodicité de la vérification du système par e2fsck, j'ai

Re: Les mystères de tune2fs et de e2fsck

ec l'aide de tune2fs > la périodicité de la vérification du système par e2fsck, j'ai supprimer la > vérification par le nombre de montage et je l'ai remplacé par un intervalle > de temps :1mois du moins c'est ce que j'espérais mais à l'usage cela ne > fonctionne pas. Ai je fait une erreur vo

Re: Les mystères de tune2fs et de e2fsck

Le 22/12/2015 12:45, MERLIN Philippe a écrit : N'arrivant pas à vous l'envoyer dans le corps du message certainement un caractère parasite, le résultat de tune2fs se trouve dans le fichier en P.J. moi je l'ai eu dans les trois messages, mais je n'ai pas la réponse :-( jdd

Re: Les mystères de tune2fs et de e2fsck

que la debian Sid > > > Kde > > > est en période d'instabilité obligeant de redémarrer le système > > > plusieurs > > > fois par jour pour pouvoir travailler, j'ai modifié avec l'aide de > > > tune2fs > > > la périodicité de la vérification du systèm

Re: e2fsck dans crontab

On Wednesday 01 July 2015 14:38:02 Sébastien NOBILI wrote: Le mercredi 01 juillet 2015 à 14:21, andre_deb...@numericable.fr a écrit : Le script du fichier binaire verifsda2 : #!/bin/bash e2fsck -p /dev/sda2 Script ou fichier binaire, il va falloir choisir. Un fichier binaire contient

Re: e2fsck dans crontab

Bonjour, il faut utiliser comme ceci pour forcer le check: e2fsck -f /dev/sda2 Le 02/07/2015 11:11, andre_deb...@numericable.fr a écrit : On Wednesday 01 July 2015 14:38:02 Sébastien NOBILI wrote: Le mercredi 01 juillet 2015 à 14:21, andre_deb...@numericable.fr a écrit : Le script du

Re: e2fsck dans crontab

Le 01/07/2015 14:21, andre_deb...@numericable.fr a écrit : Le mercredi 01 juillet 2015 à 12:01, andre_deb...@numericable.fr a écrit : J'ai mis dans crontab un fichier binaire de vérification de partition une fois par jour : # e2fsck /dev/sda2 Perso dans les scripts executes avec cron, je

Re: e2fsck dans crontab

Bonjour, Le mercredi 01 juillet 2015 à 12:01, andre_deb...@numericable.fr a écrit : J'ai mis dans crontab un fichier binaire de vérification de partition une fois par jour : # e2fsck /dev/sda2 Plus précisément, tu as ajouté une ligne de texte dans la crontab pour planifier le lancement d'une

e2fsck dans crontab

Bonjour, J'ai mis dans crontab un fichier binaire de vérification de partition une fois par jour : # e2fsck /dev/sda2 Je l'ai testé, il fonctionne très bien : #!/bin/bash e2fsck -p /dev/sda2 La partition sda2 est montée et démontée 24 fois par jour, (une fois/heure) pour sauvegarde. Lorsque je

Re: e2fsck dans crontab

andre_deb...@numericable.fr a écrit : J'ai mis dans crontab un fichier binaire de vérification de partition une fois par jour : # e2fsck /dev/sda2 Je l'ai testé, il fonctionne très bien : #!/bin/bash e2fsck -p /dev/sda2 La partition sda2 est montée et démontée 24 fois par jour, (une

Re: e2fsck dans crontab

juillet 2015 à 12:01, andre_deb...@numericable.fr a écrit : J'ai mis dans crontab un fichier binaire de vérification de partition une fois par jour : # e2fsck /dev/sda2 Plus précisément, tu as ajouté une ligne de texte dans la crontab pour planifier le lancement d'une commande, ladite commande

Re: e2fsck dans crontab

Le mercredi 01 juillet 2015 à 14:21, andre_deb...@numericable.fr a écrit : Le script du fichier binaire verifsda2 : #!/bin/bash e2fsck -p /dev/sda2 Script ou fichier binaire, il va falloir choisir. Un fichier binaire contient des données binaires qu'on ne pourra donc pas lire avec un

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

lee wrote: Kamaraju S Kusumanchi raju.mailingli...@gmail.com writes: When I ran $sudo e2fsck -c -c -f -v /dev/sdb7 I am getting a lot of errors such as Error reading block 18022401 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

On Tue, Sep 04, 2012 at 11:39:37PM +0700, Sthu Deus wrote: You have to understand: You have to connect it to the controller directly OR You can not use what the SMART offers to You. That simple. This is not actually true. Yes, the majority of USB hard drives do not support SMART, but some do.

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

Kamaraju S Kusumanchi raju.mailingli...@gmail.com writes: lee wrote: Kamaraju S Kusumanchi raju.mailingli...@gmail.com writes: When I ran $sudo e2fsck -c -c -f -v /dev/sdb7 I am getting a lot of errors such as Error reading block 18022401 (Attempt to read block from filesystem

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

Good time of the day, Jon. Thank You for Your correction. You wrote: You have to understand: You have to connect it to the controller directly OR You can not use what the SMART offers to You. That simple. This is not actually true. Yes, the majority of USB hard drives do not support

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

Good time of the day, Kamaraju. You wrote: Yes, there are I/O errors in syslog such as Aug 30 08:27:20 kusumanchi kernel: [118453.218041] Buffer I/O error on device sdb7, logical block 5384272 Aug 30 08:27:20 kusumanchi kernel: [118453.219839] Buffer I/O error on device sdb7, logical

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

Good time of the day, Kamaraju. You wrote: May be I am missing something here. The USB hard drive I am talking is very similar to http://www.amazon.com/Iomega-Prestige-Portable- SuperSpeed-35192/dp/B004NIAG5E/ref=cm_cr_pr_product_top . The case can't be removed. You have to understand: You

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

On Ma, 04 sep 12, 23:39:37, Sthu Deus wrote: Personally, I do not believe that the HDD is not extractable - speaking in general. To quote an uncle of mine, one only needs a persuader (read: hammer) :D Kind regards, Andrei -- Offtopic discussions among Debian users and developers:

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

Good time of the day, Andrei. You wrote: To quote an uncle of mine, one only needs a persuader (read: hammer) :D You have very wise uncle! :o) Sthu. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

On Thu, Aug 30, 2012 at 11:40:55PM -0400, Kamaraju S Kusumanchi wrote: Dan Ritter wrote: On Tue, Aug 28, 2012 at 09:28:20AM -0400, Kamaraju S Kusumanchi wrote: 4) What might have caused this problem and how to prevent it in the future? I don't know, but in my experience,

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

Kamaraju S Kusumanchi raju.mailingli...@gmail.com writes: When I ran $sudo e2fsck -c -c -f -v /dev/sdb7 I am getting a lot of errors such as Error reading block 18022401 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps. Ignore errory

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

Federico Alberto Sayd wrote: Did you try to diagnose your hardrive with smartmontools? Smartmontools uses S.M.A.R.T.[1] technology included in harddrives, and displays info about predictable failures, time of use, etc. Regards [1] http://en.wikipedia.org/wiki/S.M.A.R.T. $smartctl -a

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

Good time of the day, Kamaraju. You wrote: $smartctl -a /dev/sdb smartctl 5.41 2011-06-09 r3365 [i686-linux-3.0.0-1-686-pae] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net /dev/sdb: Unknown USB bridge [0x059b:0x0571 (0x000)] Smartctl: please

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

Sthu Deus wrote: You will not be able to do so until You connect Your drive to computer directly - i.e. through PATA/SATA cable. This is an external USB hard drive. The only connection it has is USB. So, I guess in this case smartctl is not much useful. -- Kamaraju S Kusumanchi

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

On Tue, Aug 28, 2012 at 09:28:20AM -0400, Kamaraju S Kusumanchi wrote: 1) Does this mean there are badblocks on my hard drive? Yes. 2) Am I correct in choosing yes to both these questions or is there a better way? Yes. 3) Is the drive going bad and need to be replaced? Yes. 4) What

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

On Thursday 30 August 2012 19:17:14 Kamaraju S Kusumanchi wrote: Sthu Deus wrote: You will not be able to do so until You connect Your drive to computer directly - i.e. through PATA/SATA cable. This is an external USB hard drive. The only connection it has is USB. So, I guess in this case

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

Kamaraju, You wrote: You will not be able to do so until You connect Your drive to computer directly - i.e. through PATA/SATA cable. This is an external USB hard drive. The only connection it has is USB. So, I guess in this case smartctl is not much useful. And You can not disassemble

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

Sthu Deus wrote: Kamaraju, You wrote: You will not be able to do so until You connect Your drive to computer directly - i.e. through PATA/SATA cable. This is an external USB hard drive. The only connection it has is USB. So, I guess in this case smartctl is not much useful. And

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

Dan Ritter wrote: On Tue, Aug 28, 2012 at 09:28:20AM -0400, Kamaraju S Kusumanchi wrote: 4) What might have caused this problem and how to prevent it in the future? I don't know, but in my experience, USB-connected hard disks suffer these problems much more than PATA/SATA/eSATA/SCSI/SAS

e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

When I ran $sudo e2fsck -c -c -f -v /dev/sdb7 I am getting a lot of errors such as Error reading block 18022401 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps. Ignore errory? yes Force rewritey? yes Error reading block 19562497 (Attempt

Re: e2fsck errror: Error reading block (Attempt to read block from filesystem resulted in short read)

On 28/08/12 10:28, Kamaraju S Kusumanchi wrote: When I ran $sudo e2fsck -c -c -f -v /dev/sdb7 I am getting a lot of errors such as Error reading block 18022401 (Attempt to read block from filesystem resulted in short read) while reading inode and block bitmaps. Ignore errory? yes Force

Re: Ayuda e2fsck

disco presento estos problemas después de varios apagones y este servidor no estaba protegido por UPS. Le realice un e2fsck pero nada. si me pueden colaborar les estaré muy agradecido. Ese disco es parte de un raid por software ? no das nada de info amen de haber solicitado ayuda en mas de 5

Ayuda e2fsck

realice un e2fsck pero nada. si me pueden colaborar les estaré muy agradecido. -- Jorge A. Toro Hoyos Ing. Teleinformático. CumbiaTIC, Dir. División de Informática COR, Esp. GNU/Linux, Esp. Desarrollo de Software. http://jolthgs.wordpress.com

Re: Ayuda e2fsck

. Le realice un e2fsck pero nada. Puedes consultar este artículo, indican cómo recuperar (siempre que sea posible) los archivos que están bajo /lost+found: *** How to recover files from lost+found after fsck in linux (How I did it in Ubuntu) http://karuppuswamy.com/wordpress/2010/06/09/how

Re: dosfslabel finds problem, e2fsck does not

On Sb, 24 iul 10, 09:18:04, Arthur Marsh wrote: xhost + This is insecure: http://www.fooishbar.org/blog/tech/x/xhost-plus-2010-06-29-22-42.html Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic

Re: dosfslabel finds problem, e2fsck does not

Andrei Popescu wrote, on 24/07/10 16:29: On Sb, 24 iul 10, 09:18:04, Arthur Marsh wrote: xhost + This is insecure: http://www.fooishbar.org/blog/tech/x/xhost-plus-2010-06-29-22-42.html Regards, Andrei Agreed about the xhost + being insecure but it took a few tries to work out the

Re: dosfslabel finds problem, e2fsck does not

. Trying to resolve this I used e2fsck to check each of the disk partitions and e2fsck reported all the partitions clean. However, the result of running dosfslabel /dev/hda1 results in the following output

Re: dosfslabel finds problem, e2fsck does not

On Sat, Jul 24, 2010 at 07:49:58PM +0930, Arthur Marsh wrote: Andrei Popescu wrote, on 24/07/10 16:29: On Sb, 24 iul 10, 09:18:04, Arthur Marsh wrote: xhost + This is insecure: http://www.fooishbar.org/blog/tech/x/xhost-plus-2010-06-29-22-42.html Regards, Andrei Agreed about the

Re: dosfslabel finds problem, e2fsck does not

the installation of linux-base. Trying to resolve this I used e2fsck to check each of the disk partitions and e2fsck reported all the partitions clean. However, the result of running dosfslabel /dev/hda1 results

Re: dosfslabel finds problem, e2fsck does not

this I used e2fsck to check each of the disk partitions and e2fsck reported all the partitions clean. However, the result of running dosfslabel /dev/hda1 results in the following output: There are differences between boot sector and its backup. Differences: (offset:original/backup

Re: dosfslabel finds problem, e2fsck does not

On Wed, 21 Jul 2010 23:42:39 +0200, Florian Kulzer florian.kulzer+deb...@icfo.es wrote: On Wed, Jul 21, 2010 at 15:53:36 -0400, Thomas H. George wrote: /dev/hda1/temp ext2rw,user,auto0 2 /dev/sdc /media/fuze vfatrw,user,noauto 0

Re: dosfslabel finds problem, e2fsck does not

. Trying to resolve this I used e2fsck to check each of the disk partitions and e2fsck reported all the partitions clean. However, the result of running dosfslabel /dev/hda1 results in the following output

Re: dosfslabel finds problem, e2fsck does not

-0400, Thomas H. George wrote: My system, Squeeze, cannot install the latest kernel image because dosfslabel finds a problem that prevents the installation of linux-base. Trying to resolve this I used e2fsck to check each of the disk partitions and e2fsck reported

Re: dosfslabel finds problem, e2fsck does not

used e2fsck to check each of the disk partitions and e2fsck reported all the partitions clean. However, the result of running dosfslabel /dev/hda1 results in the following output: There are differences between boot sector and its backup. Differences

Re: dosfslabel finds problem, e2fsck does not

a problem that prevents the installation of linux-base. Trying to resolve this I used e2fsck to check each of the disk partitions and e2fsck reported all the partitions clean. However, the result of running dosfslabel /dev/hda1 results in the following

Re: dosfslabel finds problem, e2fsck does not

, cannot install the latest kernel image because dosfslabel finds a problem that prevents the installation of linux-base. Trying to resolve this I used e2fsck to check each of the disk partitions and e2fsck reported all the partitions clean

Re: dosfslabel finds problem, e2fsck does not

:25:42 -0400, Thomas H. George wrote: My system, Squeeze, cannot install the latest kernel image because dosfslabel finds a problem that prevents the installation of linux-base. Trying to resolve this I used e2fsck to check each of the disk

dosfslabel finds problem, e2fsck does not

My system, Squeeze, cannot install the latest kernel image because dosfslabel finds a problem that prevents the installation of linux-base. Trying to resolve this I used e2fsck to check each of the disk partitions and e2fsck reported all the partitions clean. However, the result of running

Re: dosfslabel finds problem, e2fsck does not

On Tue, Jul 20, 2010 at 11:25:42 -0400, Thomas H. George wrote: My system, Squeeze, cannot install the latest kernel image because dosfslabel finds a problem that prevents the installation of linux-base. Trying to resolve this I used e2fsck to check each of the disk partitions and e2fsck

Re: dosfslabel finds problem, e2fsck does not

this I used e2fsck to check each of the disk partitions and e2fsck reported all the partitions clean. However, the result of running dosfslabel /dev/hda1 results in the following output: There are differences between boot sector and its backup. Differences: (offset:original/backup

Re: dosfslabel finds problem, e2fsck does not

that prevents the installation of linux-base. Trying to resolve this I used e2fsck to check each of the disk partitions and e2fsck reported all the partitions clean. However, the result of running dosfslabel /dev/hda1 results in the following output: There are differences

Re: dosfslabel finds problem, e2fsck does not

install the latest kernel image because dosfslabel finds a problem that prevents the installation of linux-base. Trying to resolve this I used e2fsck to check each of the disk partitions and e2fsck reported all the partitions clean. However, the result of running dosfslabel /dev

Re: e2fsck: HOWTO tutorial

On Jo, 24 iun 10, 13:16:29, Paul E Condon wrote: I was OP on a related thread a couple of months ago. I would say that I abandoned trying to understand issues of checking for errors on USB drives as a user. I did gain the impression that what I thought were hardware errors were instead more

Re: e2fsck: HOWTO tutorial

On 20100622_022612, Ron Johnson wrote: On 06/22/2010 12:33 AM, Augustin wrote: Hello, I must learn to use e2fsck as I am having some I/O problems on some of my external drives. I checked all the existing documentation everywhere I could think of (including the Debian official

e2fsck: HOWTO tutorial

Hello, I must learn to use e2fsck as I am having some I/O problems on some of my external drives. I checked all the existing documentation everywhere I could think of (including the Debian official documentation and existing HOWTOs from TLDP), but couldn't find anything that is detailed

Re: e2fsck: HOWTO tutorial

On 06/22/2010 12:33 AM, Augustin wrote: Hello, I must learn to use e2fsck as I am having some I/O problems on some of my external drives. I checked all the existing documentation everywhere I could think of (including the Debian official documentation and existing HOWTOs from TLDP

Re: e2fsck: HOWTO tutorial

On Tuesday 22 June 2010 15:26:12 Ron Johnson wrote: The *drive*? No. e2fsck checks the filesystem data structures that have been written onto the drive. Yes, sorry. I did mean the partition, not the drive. You need SMART to check the drive. Yes, I haven't had time to install

Re: e2fsck: HOWTO tutorial

On Tuesday 22 June 2010 15:26:12 Ron Johnson wrote: The *drive*? No. e2fsck checks the filesystem data structures that have been written onto the drive. Yes, sorry. I did mean the partition, not the drive. You need SMART to check the drive. Yes, I haven't had time to install

Re: e2fsck: HOWTO tutorial

On 06/22/2010 03:17 AM, Augustin wrote: On Tuesday 22 June 2010 15:26:12 Ron Johnson wrote: The *drive*? No. e2fsck checks the filesystem data structures that have been written onto the drive. Yes, sorry. I did mean the partition, not the drive. You need SMART to check the drive. Yes

Re: e2fsck: HOWTO tutorial

Augustin: On Tuesday 22 June 2010 15:26:12 Ron Johnson wrote: The *drive*? No. e2fsck checks the filesystem data structures that have been written onto the drive. Yes, sorry. I did mean the partition, not the drive. No, you didn't mean the partition, you meant the filesystem

Re: e2fsck: HOWTO tutorial

On 6/22/2010 3:47 AM, Jochen Schulz wrote: What's unclear about it? The manpage doesn't say: Okay, when this happens, run this. When that happens, run that. (That's what he wants. And, I admit, what I want, sometimes.) -- To UNSUBSCRIBE, email to

Re: e2fsck: HOWTO tutorial

On Tue, Jun 22, 2010 at 1:33 PM, Augustin beginner2...@masquilier.org wrote: Hello, I must learn to use e2fsck as I am having some I/O problems on some of my external drives. I checked all the existing documentation everywhere I could think of (including the Debian official documentation

comme un upgrade après e2fsck

Bonjour, A la suite d'un figeage du PC sous Debian Lenny, j'ai fait un reboot hardware et ai lancé e2fsck /dev/sd.. Le système a fait un fix de nombreux inodes, qui a été réparé. Après le reboot, je constate que l'esthétique du bureau a changé, ainsi que celle de plusieurs applis ... comme si

TR: comme un upgrade après e2fsck

-- msg original -- Sujet: comme un upgrade après e2fsck De: cor...@free.fr Date: 2010.04.12 15:51 )Le système a fait un fix de nombreux )inodes, qui a été réparé. )Après le reboot, je constate que )l'esthétique du bureau a changé, Voir Aptitude reinstall Avec un peu de chances ta base de

Re: lvm2 and e2fsck

Mark Allums wrote: Ron Johnson wrote: On 02/23/2009 01:52 AM, Mark Allums wrote: [snip] 0. I have lvm2 running on top of Linux md RAID, and don't actually have any ext4 file sytem partitions to check, so that particular fsck command was destined to fail. But it shows it's there, when it's

Re: lvm2 and e2fsck

On 02/24/2009 06:21 AM, Mark Allums wrote: Mark Allums wrote: Ron Johnson wrote: On 02/23/2009 01:52 AM, Mark Allums wrote: [snip] 0. I have lvm2 running on top of Linux md RAID, and don't actually have any ext4 file sytem partitions to check, so that particular fsck command was destined

Re: lvm2 and e2fsck

On Tuesday 24 February 2009 11:49:26 am Ron Johnson wrote: Though, are there any commands which would indicate whether my LV or VGs are screwed up? (Fixing them might allow me to get my data back.) Do you think that your volume descriptors got hosed? The main LVM diagnostic commands are:

Re: lvm2 and e2fsck

On 02/24/2009 03:34 PM, Matthew Moore wrote: On Tuesday 24 February 2009 11:49:26 am Ron Johnson wrote: Though, are there any commands which would indicate whether my LV or VGs are screwed up? (Fixing them might allow me to get my data back.) Do you think that your volume descriptors got

Re: lvm2 and e2fsck

On Tuesday 24 February 2009 02:44:14 pm Ron Johnson wrote: This looks reasonable. # lvdisplay Logging initialised at Tue Feb 24 15:42:45 2009 Set umask to 0077 lvdisplayFinding all logical volumes lvdisplay --- Logical volume --- lvdisplay LV Name

Re: lvm2 and e2fsck

On 02/24/2009 06:15 PM, Matthew Moore wrote: On Tuesday 24 February 2009 02:44:14 pm Ron Johnson wrote: [snip] No, I definitely have /sbin/fsck.ext4. But running it doesn't fix the group descriptor error? This person is having the same problem and looks to have resorted to dumping the fs

Re: lvm2 and e2fsck

On 02/23/2009 01:52 AM, Mark Allums wrote: [snip] 0. I have lvm2 running on top of Linux md RAID, and don't actually have any ext4 file sytem partitions to check, so that particular fsck command was destined to fail. But it shows it's there, when it's needed. Except this was a virgin fs,

Re: lvm2 and e2fsck

Ron Johnson wrote: On 02/23/2009 01:52 AM, Mark Allums wrote: [snip] 0. I have lvm2 running on top of Linux md RAID, and don't actually have any ext4 file sytem partitions to check, so that particular fsck command was destined to fail. But it shows it's there, when it's needed Except

lvm2 and e2fsck

Hi, # mount -v -t ext4 /dev/main_huge_vg/main_huge_lv /data/big $ dmesg | tail -n2 EXT4-fs: ext4_check_descriptors: Block bitmap for group 0 not in group (block 3120627712)! EXT4-fs: group descriptors corrupted! Can I just do this? # e2fsck /dev/main_huge_vg/main_huge_lv -- Ron Johnson, Jr

Re: lvm2 and e2fsck

Ron Johnson wrote: Hi, # mount -v -t ext4 /dev/main_huge_vg/main_huge_lv /data/big $ dmesg | tail -n2 EXT4-fs: ext4_check_descriptors: Block bitmap for group 0 not in group (block 3120627712)! EXT4-fs: group descriptors corrupted! Can I just do this? # e2fsck /dev/main_huge_vg/main_huge_lv

Re: lvm2 and e2fsck

this? # e2fsck /dev/main_huge_vg/main_huge_lv You know the usual rules about fsck'ing a mounted file system? Yup... ext4 reduces to ext3, or even ext2 as long as you haven't use extents (and the journal's reasonably clean). Yep. So yes. That's what I thought. Haven't they added ext4

Re: lvm2 and e2fsck

corrupted! Can I just do this? # e2fsck /dev/main_huge_vg/main_huge_lv You know the usual rules about fsck'ing a mounted file system? Yup... ext4 reduces to ext3, or even ext2 as long as you haven't use extents (and the journal's reasonably clean). Yep. So yes. That's what I thought

Re: e2fsck /dev/md0 issues

confused. It's complaining about bad partition or superblock. You said I need to resize my fs, but according to fdisk, they are the same. Aren't they? Your filesystem isn't on raw partitions. It is on the /dev/md0 device. That device is 244189984 blocks, as e2fsck told you. You could also use

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

On Saturday 2008 December 20 22:42:10 M.Lewis wrote: The filesystem size (according to the superblock) is 24419 blocks ^ The physical size of the device is 244189984 blocks ^

Re: e2fsck /dev/md0 issues

Boyd Stephen Smith Jr. wrote: On Saturday 2008 December 20 22:42:10 M.Lewis wrote: The filesystem size (according to the superblock) is 24419 blocks ^ The physical size of the device is 244189984 blocks

Re: e2fsck /dev/md0 issues

complaining about bad partition or superblock. You said I need to resize my fs, but according to fdisk, they are the same. Aren't they? Your filesystem isn't on raw partitions. It is on the /dev/md0 device. That device is 244189984 blocks, as e2fsck told you. You could also use blockdev

  1   2   3   >