similar to: Killed my filesystem?! (data moved to lost&found)

Hi! We have a server still running Debian 3.0 (Woody) that nobody likes to touch for maintenance ... ;) Our home-directories are located on a separate HDD (30GB, 1 large primary ext3 partition) and until yesterday it worked correctly. Because the partition was nearly full we had to enlarge our home-space by moving it to a larger HDD. We decided to try a copy of whole partition by using

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:

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

I installed 4.4 on a machine that's got two RAID volumes, one of which is a bit over 2.1 terabytes. The installer had no problem. However, fsck does. Commenting out the volume in /etc/fstab, the machine will boot. The machine will mount the volume and use it. Everything seems fine except fsck, which seems, well, fscked. When trying to run fsck, it says: # fsck /dev/sdb1 fsck 1.35

Thank you to all who replied. I am very happy (for you guys anyway) to report that this was NOT infact caused by ext3, but rather a very very untimely memory failure that occured during my convertion from ext2 to ext3. It turned out that one of my PC2100 DDRs went south, and I'll be contacting Crucial to deal with that. Thanx again for all the help. benr. -----Original Message-----

Hi, I just tried the 2.6.22-r1 candidate to test whether some bug I have hit in the past still exists. I did use 2.6.20.6 so far. So, I have cleanly rebooted to use the new kernel, after the machine came up I tried to mess with the bug, and had to reboot again to play with kernel commandline parameters. Unfortunately, on the next reboot fsck was schedules on my filesystem after 38 clean

I will use this topic to post all of my problems with wine (I decided that's better than opening a lot of stupid posts that only spam this forum) (to admins: You can delete this topic if you think it's inappropriate) I'm having a lot of problems with wine (maybe some of it is similar to yours, so this is kind of DONT'S that you don't want ot do on your computer) My first

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

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

[sorry if this isn't threaded right... I just subscribed] Theodore Ts'o wrote: > > There are two reasons for the reserve. One is to reserve space on the > partition containing /var and /etc for log files, etc. The other is > to avoid the performance degredation when the last 5-10% of the disk > space is used. (BSD actually reserves 10% by default.) Given that > the

Dear ext3-users, we hit this condition in fs/ext3/inode.c:ext3_block_to_path() if (i_block < 0) { ext3_warning (inode->i_sb, "ext3_block_to_path", "block < 0"); occasionally on two 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

Hi, Sorry if this is an old and fixed issue but I can't really seem to find a definitive explanation/fix to this in the mail lists. Ever since I upgraded to FC2 my server randomly decides that it can no longer access the disk and "aborts" the ext3 journal leaving it read-only as expected. I've seen the same errors on other mail list, explained away as disk or disk cable

I have several CentOS5 hosts in a VMware ESX 3.5.0 226117 environment using iSCSI storage. Recently we've begun to experience journal aborts resulting in remounted-read-only filesystems as well as other filesystem issues - I can unmount a filesystem and force a check with "fsck -f" and occasionally find errors. I've found -

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

On 27/03/2019 16:12, Timo Sirainen wrote: > On 27 Mar 2019, at 14.58, Timo Sirainen via dovecot <dovecot at dovecot.org > <mailto:dovecot at dovecot.org>> wrote: >> >>> dovecot isn't able to auto fix the indexes and manual deletion is >>> required in all such cases >> >> So if it keeps repeating, it's very strange. Could you send me

Judging from the frequency of my messages here one could think that I'm too stupid to upgrade a workstation to 5.2 (but the servers I've tried work without problem) OK. The problem: I've tried to upgrade a 5.1-x86_64-workstation to 5.2. During the upgrade immidiatly after (according to the /var/log/messages) upgrading the two (64 & 32-bit) libgcc-packages an EXT3-error occurs and

On Monday August 4, akpm@osdl.org wrote: > Daniel Jacobowitz <dan@debian.org> wrote: > > > > I came back this morning and found: > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted >

Hi, I found the following in my logfiles: The failure is not reproducable at the moment. System is delivering mails to mailboxes with no problems at all. It is a production installation with medium load. dovecot --version: 1.1.7 OS: Linux (Gentoo/x86 stable) - grsec enabled kernel deliver.log: deliver(user at example.tld): Panic: file istream-tee.c: line 144 (i_stream_tee_read): assertion

ext3 is having big problems on my x86-64 system. An ext3 partition has just gone crazy, with the following messages in dmesg: EXT3-fs error (device hda3): ext3_readdir: bad entry in directory #4603905: rec_len % 4 != 0 - offset=0, inode=2507704792, rec_len=42, name_len=0 Aborting journal on device hda3. ext3_abort called. EXT3-fs abort (device hda3): ext3_journal_start: Detected aborted journal

Hello. I have a Samba share pointing to a mount point which is mounted read-only on boot. It has since been remounted as R/W. The share itself is marked as writable in smb.conf : [storage] path = /mnt/storage/ guest ok = yes browseable = yes writable = yes After connecting to the share via CIFS as an authenticated user, I get a "permission denied" message, with the error code being