similar to: EXT3 corruption when FS is full

libswfdec/swfdec_as_object.c | 64 libswfdec/swfdec_file_reference.c | 2 libswfdec/swfdec_load_object.c | 81 libswfdec/swfdec_sprite_movie_as.c | 19 libswfdec/swfdec_system_security.c | 1 test/trace/Makefile.am | 72

Hello I found that after defrag a file, the corresponding inode's i_blocks become incorrect. I hope following description address the real reason. i_blocks is decreased in 'btrfs_drop_extents' when something are drop/truncated and 'run_delalloc_range' calls 'btrfs_drop_extents' at first place, so 'run_delalloc_range' may decrease the i_blocks.

Fix "h_buffer_credits<0" assert failure during truncate. The bug occurs when the "i_blocks" count in the file's inode overflows past 2^31. That works fine most of the time, because i_blocks is an unsigned long, and should go up to 2^32; but there's a place in truncate where ext3 calculates the size of the next transaction chunk for the delete, and that mistakenly

I have many systems running current ext3 code. Some of them have hardware problems that lead to frequent reboots, and the journal recovery has worked excellently. However, on the periodic forced fsck on supposedly recovered and clean filesystems, I've many times seen fsck report that i_blocks is too large in one or more inodes. I suspect that i_blocks is somehow escaping proper restoration

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

This fixes the "i_blocks went wrong when the disk filled up" problem. In ext3_new_block() we increment i_blocks early, so the quota operation can be performed outside lock_super(). But if the block allocation ends up failing, we forget to undo the allocation. This is not a serious bug, and probably does not warrant an upgrade for production machines. Its effects are: 1) errors are

I am using SuSE 7.3 compiled ext3 support into the kernel and installed it. All my partitions load up as ext3 except / . I ran tune2fs several times, still doesn't take on the / drive. Most recent dumpe2fs -h show no features on that drive=, I keep going around in circles, removing .journal from / and running tune2fs but it never works for / What am I doing wrong? ( thanks in advance)

Hello, I've got a problem that is not solved after an e2fsck. What happens is that the kernel (vanilla 2.6.12) does this: journal_bmap: journal block not found at offset 1036 on hda6 Aborting journal on device hda6. ext3_abort called. The filesystem is mounted with errors=panic, so the system reboots. At boot-up an e2fsck is run on /dev/hda6. Sometimes it finds errors, sometimes not.

Hi, I've tried a couple of different versions/distros and can't seem to mount a FAT32 (vfat) partition and then share it with Samba, such that all use of R/A/S/H attributes (for files and folder) is maintained... So I'm wondering if this is even possible? I've most recently been testing with host: Debian 4.0 (Linux 2.6.18-4-686) which includes Samba 3.0.24 client: WinXP

I appear to have a broken filesystem on this box to the point where I am probably going to rebuild the system since I have lost trust in it.... I was wondering if there was any reasonable postmortum work I could do on it before it gets rebuilt. History is that the laptop has a much mauled partition set on it - initially it came with 100% win2k, I then shrunk that and added linux (a RH71 install

Hi, I tried to convert my root partition from an ext2 to ext3 fs using tune2fs. I'm running a 2.4.10 kernel with ext3 support, but the partition is not mounted ext3. In fact the journal feature is missing from the superblock: # cat /proc/filesystems | grep ext ext3 ext2 # tune2fs -l /dev/hda6 | grep features Filesystem features: filetype sparse_super # ls -l /.journal

Al writes: > On Thu, 22 Mar 2001, Andreas Dilger wrote: > > If this is the case, then all of the other zero initializations can be > > removed as well. I figured that if most of the fields were being > > zeroed, then ones _not_ being zeroed would lead to this problem. > > Other zero initializations in inode->u certainly can be > removed, but whether it's

Hello everybody, I''m playing with Xen and trying to extend DomU disk space. My Configuration: Dom0: all Xen machine are HVM. They''re installed on LVM. I''ve one VG (XEN) on Dom0 and created a LV (here, xps.101.disk) per DomU. disk configuration in xen conf is as follow: disk = [ ''phy:/dev/XEN/xps.%d.disk,ioemu:hda,w'' % (vmid)

/an ocfs2 bug: a truncate races with ocfs2_get_block(...,0). 1) 'dd' is doing a truncate, clearing the page cache and reset inode size./ /2) between clearing page cache and resizing inode, a read comes and create a / /new page and insert it to page cache./ /3) the read(from `cat`) set buffer head in the new page as mapped but doesn't increase / /ip_mmu_private in ocfs2_get_block()

Hi! I''ve just installed xen from source (had a prebuilt install before). Just made ''make world'' and ''make install'' and tried to reuse an old domU. But while booting an fsck error appears. ---------------------------- fsck.ext3: No such file or directory while trying to open /dev/hda6 /dev/hda6: The superblock could not be read or does not describe a

Hi, I was trying to run a guest OS with multiple partitions. I added a line like disk=[''phy:hda6,hda6,w''] in the configuration file. The disk was not mounted in the host OS. However, the kernel refuses to boot with an error message which says "kernel not syncing... attempted to kill init... rebooting...". When I remove that line, everything works. Is there

Hello, I just went back to 2.4.9-ac18 from 2.4.10 (i386), and then for the first time migrated all my ext2 partitions to ext3. I did this over a series of reboots, as I confirmed that indeed things continued to work. The last step I took was to convert /. I have set up /etc/fstab to mount my 'ext3' partitions with 'auto', I suppose thinking this will make it easier to roll

Background: This is a dual boot (Windows XP and CentOS 5.2 (32 bit) box. There were four (4) NTFS partitions. The C partition got full. I deleted the 4 NTFS partitions and did a clean install of Windows XP, into one (1) NTFS partition. I knew that I would need to install GRUB again and I did that, using the CentOS 5 Installation DVD. When I tried to boot into Linux, no joy. this is the GRUB error

On Wed, Dec 9, 2015 at 1:07 PM, Emilio Lazo Zaia via Syslinux <syslinux at zytor.com> wrote: > I thought I've found three bugs on syslinux 6.03: Just to be clear, is this only affecting vesamenu.c32? > (1) With sample config file as is, i.e. leaving commented MENU VSHIFT and > MENU COLOR UNSEL but uncommented MENU COLOR SEL: > > A black "border" is displayed

Here I don't want to start a discussion, but rather share a *solution* that took me some days to come up with. The whole stuff started with a power-outage. After reboot, my server (ext3) came back with the dreaded file system error (Ctrl-D to reboot or password for maintenance) - if you've never seen this, consider yourself lucky! In any case, I did the fsck as prescribed, but abandoned