similar to: Policy after fsck fixes errors

Greetings! Need your help fellow penguins! Strange behavior with fsck.ext3: how to remove a long orphaned inode list? After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting itself and then trying to correct

Hello, This may be a slightly rambling and inexpert question from point of view of the learned folks on this list - feel free to go and read something more interesting, but I am curious and a little alarmed about a recent event. I am running Linux from Scratch ("LFS"), under a locally compiled Kernel 2.4.20 (SMP). The root filsytem was created as ext2 and converted to ext3 with an

Hello. Is there a simple way, at a shell script level, of finding out whether an ext3 fs has a sane journal, other than mounting it or running a full fsck ? I may quite well be missing a few things here, but what I think I'd like is some option extra to e2fsck that says "if this is a journalled filesystem, and it was shut down uncleanly, just replay the journal and check for immediately

Every 24 mounts, fsck runs. Often enough, this run will fail demanding a manual run. This -f manual runs goes through its stages and only on rare occasion finds an orphaned node. 99%, finds noting amiss. Any reason for these "failures"?

On Fri, March 10, 2017 11:57, m.roth at 5-cent.us wrote: > > Looks like only one sector's bad. Running badblocks should, > I think, mark that sector as bad, so the system doesn't try > to read or write there. I've got a user whose workstation has > had a bad sector running for over a year. However, if it > becomes two, or four, or 64 sectors, it's replacement

On 08/11/2017 12:16 PM, Chris Murphy wrote: > On Fri, Aug 11, 2017 at 7:53 AM, Robert Nichols > <rnicholsNOSPAM at comcast.net> wrote: >> On 08/10/2017 11:06 AM, Chris Murphy wrote: >>> >>> On Thu, Aug 10, 2017, 6:48 AM Robert Moskowitz <rgm at htt-consult.com> >>> wrote: >>> >>>> >>>> >>>> On

Hi, Recently I've decided to play with gjournal. Main reason was a promise of avoiding full fsck check after unclean shutdown. I've successfuly configured gjournal on existing filesystems (all UFS). And then it happened - my system had a power failure. After boot, it forced me to run fsck manualy. Nothing special, I did it before... But this time it failed on gjournaled disks.

Hi, I'm running kernel 2.6.8-15, lvm2 v2.01.04-5 and acl v2.2.23-1 on a Sunblade 100 (sparc). In a few months we have experienced for several times that an ext3 filesystem is remounted as read-only (this is due to the option "errors=remount-ro" in /etc/fstab). Sometimes there is no error in log files but sometimes we see: kernel: init_special_inode: bogus i_mode (3016) kernel:

Hello. My box has been running flawlessly for months now, but in the last 2 days hasn't stayed up for more than 5 minutes. All this seemed to have started after I did a very very bad thing...... I ran the EXT2 to EXT3 conversion on my root filesystem. I used the "tune2fs -j /dev/sda1" to do the deed. After it completed the machine ran fine (the machine was up and serving when I

Hi List, i'd like to share with you what happened yesterday. Kernel 2.6.36.1 ocfs2-tools 1.6.3 (latest). I had an old OCFS2 partition created with a 2.6.32 kernel and ocfs2 tools 1.4.5. I unmounted all partitions on all nodes in order to enable discontig-bg. I then used tunefs to add discontig-bg, inline-data and indexed-dirs. During indexed-dirs tunefs segfaulted and since then, fsck

On 08/10/2017 11:06 AM, Chris Murphy wrote: > On Thu, Aug 10, 2017, 6:48 AM Robert Moskowitz <rgm at htt-consult.com> wrote: > >> >> >> On 08/09/2017 10:46 AM, Chris Murphy wrote: >>> If it's a bad sector problem, you'd write to sector 17066160 and see if >> the >>> drive complies or spits back a write error. It looks like a bad sector

Hello! I''ve a ubuntu server running over a HVM DomU. After a hang, the domU doesn''t start again. The domU was not able to mount the virtual machine disk so I started with a live cd and I tried to mount the disk root part / with no success so I ran fsck.ext3 and it gave me input/output error in the domU and in dom0 the kernel says: Feb 14 18:22:28 scofield last message

Dear All My CentOS server got file system inconsistency , asking for "type Ctrl-D for normal boot or give root password for maintenance to run fsck manually". I tried for manually run fsck , as the followings : #fsck -s /dev/hda3 But after rebooting the server it will come back again at the similar prompt asking for "give root password for maintenance" . Can you please do me

We have a very old Dell desk top machine that has been running CentOS 6 for the past five years.? It received a new, 1 TB disk and additional memory before the OS installation.? It has been the primary Linux machine in our smallest and most remote field office.? It has been updated at least once a week and has all current dates installed. Boot-up this morning lasted about six times as long as

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This patch-set introduces the CAIF Virtio Link layer driver. This driver depends on Rusty's new host virtio ring implementation, so this patch-set is based on the vringh branch in Rusty's git. Regards, Sjur cc: Rusty Russell <rusty at rustcorp.com.au> cc: Ohad Ben-Cohen <ohad at wizery.com> cc: David S. Miller

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This patch-set introduces the CAIF Virtio Link layer driver. This driver depends on Rusty's new host virtio ring implementation, so this patch-set is based on the vringh branch in Rusty's git. Regards, Sjur cc: Rusty Russell <rusty at rustcorp.com.au> cc: Ohad Ben-Cohen <ohad at wizery.com> cc: David S. Miller

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This driver depends on Rusty's new host virtio ring implementation, so this patch-set is based on the vringh branch in Rusty's git. Changes since V1: - Use the new iov helper functions, and simplify iov handling. However this triggers compile warnings, as it takes struct iov while kernel api uses struct kiov - Introduced

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This driver depends on Rusty's new host virtio ring implementation, so this patch-set is based on the vringh branch in Rusty's git. Changes since V1: - Use the new iov helper functions, and simplify iov handling. However this triggers compile warnings, as it takes struct iov while kernel api uses struct kiov - Introduced

Something seems to be wrong with my file systems, and I want to fsck everything. But I cannot. The setup consists of 2 hds, carrying 3 raid1 (ext3) file systems (boot, /, swap). OS is up-to-date CentOS 5. So I boot from CentOS 5.3 dvd in rescue mode, do not mount the file systems, and try to run fsck -y /dev/md0 fsck -y /dev/md1 fsck -y /dev/md2 For each try I get an error message:

Hi, We've got some units in client's vehicles which are running Fedora core 1. We've can log into them over ssh remotely there is no console attached to them. I suspect one of them has some filesystem corruption, and I'd like to both force a fsck at next reboot (which I think I can do with shutdown -F) but I'd also like to make this fsck not require any human intervention.