search for: fscked

...t down uncleanly, just replay the journal and check for immediately obvious problems, but don't bother scanning the whole filesystem unless there's a '-f' in sight". AFAICT, the usual way of handling ext3 filesystems seems to be to mark them with fs_passno=0, so they never get fscked from the init scripts - but the journal gets replayed, and a few things get checked at mount time. If mount fails - because something horrible really did happen - then the /etc/rc.sysinit doesn't seem to have any way of coping, or dropping to an interactive shell. John.

...ple.tld>, orig_to=<localalias>, relay=dovecot, delay=0.38, delays=0.03/0/0/0.35, dsn=5.3.0, status=bounced (Command died with signal 6: "/usr/libexec/dovecot/deliver") Neither the grsec.log nor dmesg said anything special. The box had filesystem issues a month ago. I sucessufly fscked it. Do you think its a hidden fs problem or a dovecot issue? Here in Germay the time is at 0:30, I'll sleep some hours until I can respond to "need more information request (conf-file, or so)" Thx in advance! Markus Schirp

...uence. 3w-9xxx: scsi1: ERROR: (0x06:0x002B): Controller reset failed during scsi host reset. sd 1:0:0:0: scsi: Device offlined - not ready after error recovery This of course leads to a several hour downtime as the system has to be powered down (not just rebooted) and then the volume needs to be fscked. I've been back and forth with both the vendor and (via the vendor) 3ware with this. The card has been replaced, as well as the whole system. I'm running the latest firmware and drivers from 3ware. Have other folks had good luck with this card? What sorts of configs are you running?...

...y EXT3-fs error (device hda3) in start_transaction: Journal has aborted EXT3-fs error (device hda3) in start_transaction: Journal has aborted [...] I hit a similar problem yesterday, but lost some details so I couldn't make a proper bug report. However, it did mean that the partition got fully fscked, so I think these errors are ext3 getting confused all by itself, rather than it complaining about an already-corrupt filesystem. There's no sign of any hardware problems with the disk or controller in the logs. No extra ext3 parameters were set when mounting this partition originally. Going...

Hello, Yesterday evening this box crashed and, for once, ext3 was not able to recover automatically. There was an "unexpected inconsistency inode xxxxx has imagic flag set" error and the system would not boot. I fscked from my rescue disk and I guess 20 or 30 errors were fixed by me just selecting "y" at the prompt. The system then booted and, so far as I can tell, the only problem was that my firefox profile was corrupt (I have a feeling that an old configuration got restored instead of the current on...

...Jun 23, 2020 at 01:30:07PM +0200, Joerg Roedel wrote: > But you cannot do a recursion check in #VC, because the NMI can happen > on the first instruction of #VC, before we can increment our counter, > and then the #VC can happen on NMI because the IST stack is a goner, and > we're fscked again (or on a per-cpu variable we touch in our elaborate > NMI setup, etc..). No, the recursion check is fine, because overwriting an already used IST stack doesn't matter (as long as it can be detected) if we are going to panic anyway. It doesn't matter because the kernel will not lea...

...not reboot. At least it seemed to run fine untill about 2 hours later when it crashed. When I tried to boot FSCK couldn't complete. It would hang, crash, or just refuse. I then booted off a RH7.2 isntall CD ("rescue linux") with which I used debugfs to remove the journal and I then fscked it. The first pass with FSCK reported something about finding a journal block on the EXT2 filesystem and do I want to clear it? I figured this was probly a big part of my problem, so I cleared it and then completely refscked the disk. I mounted the filesystem to make sure /etc/fstab wouldn't...

...error" when fdatasync_path fails: deliver(user): Apr 10 14:53:20 Error: fdatasync_path(/Volumes/MailData/ user/new) failed: Too many open files in system deliver(user): Apr 10 14:53:20 Info: msgid=<...>: save failed to INBOX: BUG: Unknown internal error 2. Index files should not be fscked when they could not be opened due to ENFILE: Error: IMAP(user): open() failed with index file /Volumes/MailData/ user/.Deleted Messages/dovecot.index: Too many open files in system Warning: IMAP(user): fscking index file /Volumes/MailData/ user/.Deleted Messages/dovecot.index 3. Dovecot shoul...

On Tue, Jun 23, 2020 at 01:07:06PM +0200, Peter Zijlstra wrote: > On Tue, Apr 28, 2020 at 09:55:12AM +0200, Joerg Roedel wrote: > So what happens if this #VC triggers on the first access to the #VC > stack, because the malicious host has craftily mucked with only the #VC > IST stack page? > > Or on the NMI IST stack, then we get #VC in NMI before the NMI can fix > you up.

.../dev/vg00/virt-smtp1-root,0301,w'', ''phy:/dev/vg00/virt-smtp1-swap,0302,w'' ]" (the type was that the same Dom0 block device is used twice in the first example) Which was working great until I did a ''mkswap /dev/hda2'' inside the domain, which really fscked things up :( Given that there is almost no way you would ever want to publish the same block device to the same virtual domain more than once, would there be any value in flagging that as an error when you try and start the domain? Thanks James _______________________________________________ X...

...tain data structures that contain, well, time types. Your proposal has a n?n-zero chance to bring these issues to i386 (and other architectures). Thanks, //mirabilos -- <ch> you introduced a merge commit ?<mika> % g rebase -i HEAD^^ <mika> sorry, no idea and rebasing just fscked ?<mika> Segmentation <ch> should have cloned into a clean repo ? fault (core dumped) <ch> if I rebase that now, it's really ugh ?<mika:#grml> wuahhhhhh

...ed which panics the VM. That > also fixes the #VC-in-early-NMI problem. But you cannot do a recursion check in #VC, because the NMI can happen on the first instruction of #VC, before we can increment our counter, and then the #VC can happen on NMI because the IST stack is a goner, and we're fscked again (or on a per-cpu variable we touch in our elaborate NMI setup, etc..). There is no way I can see SNP-#VC 'work'. The best I can come up with is 'mostly', but do you like your bridges/dikes/etc.. to be mostly ok? Or do you want a guarantee they'll actually work? I'll...

...PM +0200, Joerg Roedel wrote: > > > But you cannot do a recursion check in #VC, because the NMI can happen > > on the first instruction of #VC, before we can increment our counter, > > and then the #VC can happen on NMI because the IST stack is a goner, and > > we're fscked again (or on a per-cpu variable we touch in our elaborate > > NMI setup, etc..). > > No, the recursion check is fine, because overwriting an already used IST > stack doesn't matter (as long as it can be detected) if we are going to > panic anyway. It doesn't matter becaus...

...wo identical PATA-IDE disks copied over per filesystem-rsync. What is the impact of this condition? - Kernel was 2.6.13.4, CONFIG_LBD is not set but CONFIG_HIGHMEM4G=y (I can provide further details, if required) - S.M.A.R.T meant everything is ok on both disks. - Machine has been rebooted and fscked (180 days without reboot). - Result of this fsck is not known. The condition didn't happen after this anymore. Regards Ingo Oeser -- Ingo Oeser axxeo GmbH Tiestestr. 16, 30171 Hannover Tel. +49-511-4753706 Fax. +49-511-4753716 mailto:support at axxeo.de

...ut an fsck. Some time ago I noticed, that it had "lost" 10gb (avail 0mb, used 290gb, size 300gb). So I tried to unmount the partition and do a fsck. But the partition was "busy", so I did a umount -l on that partition (yes I know now that this wasn?t the best idea at all) and fscked -y it. The fsck linked many inodes to lost&found, but I thought "fsck does know what it?s doing" ;) After this I remounted the partition and found it COMPLETLY EMPTY :(, except of thousands of files with funny names like "#31604834" in lost&found. So to my question:...

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"?

Hi all, I'm running ext3 with Linux 2.4.19pre5aa2 (and thus ext3 0.9.17) and e2fsprogs 1.27 on an x86 laptop with an IDE disk (with DMA enabled). The partition in question was mounted with the data=journal and nosuid options set. All the partitions are set to be fscked on bootup every 30 days (although I don't think this is strictely necessary, better safe than sorry). ext3 has been working fine for a number of months. Earlier today, I rebooted the system (AFAIK, the partition in question unmounted cleanly, although I wasn't paying attention to it partic...

...not reboot. At least it seemed to run fine untill about 2 hours later when it crashed. When I tried to boot FSCK couldn't complete. It would hang, crash, or just refuse. I then booted off a RH7.2 isntall CD ("rescue linux") with which I used debugfs to remove the journal and I then fscked it. The first pass with FSCK reported something about finding a journal block on the EXT2 filesystem and do I want to clear it? I figured this was probly a big part of my problem, so I cleared it and then completely refscked the disk. I mounted the filesystem to make sure /etc/fstab wouldn't...

My company recently changed its name, and now I've been asked to change our domain's name, too. Is there any way I can accomplish this without having to have each PC join a new domain, with all the problems inherent in something like that? Registry edits, etc., would be fine, but I really dread having to mess with all the profiles that are going to get messed up... Thanks! Ken

...ex_lock_timeout = false, index_delete_requested = false, index_deleted = false, log_sync_locked = true, readonly = false, mapping = true, syncing = false, need_recreate = false, index_min_write = false, modseqs_enabled = false, initial_create = false, initial_mapped = false, fscked = true } (gdb) -- Arkadiusz Mi?kiewicz, arekm / ( maven.pl | pld-linux.org )