similar to: [PATCH]Add rollback support for the converter

No material changes are made. --- Makefile | 10 +- convert.c => convert/convert.c | 803 +--------------------------------------- convert/convert.h | 76 ++++ convert/ext2.c | 791 +++++++++++++++++++++++++++++++++++++++ 4 files changed, 873 insertions(+), 807 deletions(-) rename convert.c => convert/convert.c (74%) create mode

Hello, There is a new feature ''uninitialized block groups'' in ext4. Block and inode bitmaps in uninitialized block groups are uninitialized. This confuses the converter. The fix is call ext2fs_new_inode for each block group at open time. It set up uninitialized block and inode bitmaps appropriately. This patch also contains some other minor fixes. Thank you, Signed-off-by: Yan

I have a 1.5 TB (1,475,720,773,632) partition that I wanted to convert from ext4 to btrfs. It is currently used as / for ubuntu 10.10. I booted into 11.04 beta2 and tried a ''btrfs-convert /dev/sdc1'', but after about 20 minutes it segfaulted. I performed a: sck.ext4 -cDfty -C 0 /dev/sdc1 After everything was clean, I downloaded the debugging symbols for btrfs-convert and

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, please apply the following patch to fix building btfs-progs on alpha and ia64 from: git://git.debian-maintainers.org/git/daniel/btrfs-tools.git - ---snip--- commit 561e811286c52f141cf4944fe219e6b61fab0ac9 Author: Daniel Baumann <daniel@debian.org> Date: Sat Jun 5 08:53:46 2010 +0200 Properly cast and avoid compiler warnings,

Hi, I've been writing some optimization passes for LLVM and had good luck with the simple stuff, but I am running into all kinds of trouble trying to make copies of variables within a BasicBlock as part of a LoopPass I am trying to make copies of the variables that are in scope in the loop body like so: //Remove the existing terminator

We can reproduce this oops via the following steps: $ mkfs.btrfs /dev/sdb7 $ mount /dev/sdb7 /mnt/btrfs $ for ((i=0; i<3; i++)); do btrfs sub snap /mnt/btrfs /mnt/btrfs/s_$i; done $ rm -fr /mnt/btrfs/* $ rm -fr /mnt/btrfs/* then we''ll get ------------[ cut here ]------------ kernel BUG at fs/btrfs/inode.c:2264! [...] Call Trace: [<ffffffffa05578c7>] btrfs_rmdir+0xf7/0x1b0

I removed this in an earlier commit and I was wrong. Because compression can return from filemap_fdatawrite() without having actually set any of it''s pages as writeback() it can make filemap_fdatawait() do essentially nothing, and then we won''t find any ordered extents because they may not have been created yet. So not only does this make fsync() completely useless, but it will

Hi, This branch contains the new ext4's inline data support which has been added recently to kernel 3.8. In addition to inline data support, there are other patches that remove trainling whitespaces and extra new lines in ext2fs code and the other adds an assert() macro to Syslinux core. I think it's worth mentioning that these changes were made against master branch.

This patch introduce extent buffer cache for every i-node. By this way, we can save the search time and reduce the lock contention of the root because we needn''t search the item from the root of b+ tree. Implementation: - add two pointers of extent buffer into btrfs_inode struct, one for nodes/leaves of fs/file tree, the other for nodes/leaves of the log tree. - add a variant to tell

The ext2 filesystem supports volume UUID now. The FSUUID variable can be set to kernel command line. Patch is based on FSUUID for FAT patch. Signed-off-by: Serj Kalichev <serj.kalichev at gmail.com> --- core/fs/ext2/ext2.c | 40 +++++++++++++++++++++++++++++++++++++++- core/fs/ext2/ext2_fs.h | 1 + 2 files changed, 40 insertions(+), 1 deletion(-) diff --git a/core/fs/ext2/ext2.c

As per ext4 specification: > In ext2, ext3, and ext4 (when the 64bit feature is not enabled), the > block group descriptor was only 32 bytes long and therefore ends at > bg_checksum. On an ext4 filesystem with the 64bit feature enabled, the > block group descriptor expands to at least the 64 bytes described below; > the size is stored in the superblock. Since block group

Document those places in the btrfs code which are BUGing on non-fatal error conditions that should be handled by proper error paths. This makes it easier to distinguish between what needs fixing versus which BUG_ON''s we might want to keep (to trap code bugs, unexpected inconsistencies, etc). Do this with a trivial macro, ''btrfs_fixable_bug_on'' which just defines to

As the subject says, building syslinux fails when built against 2.6.8.1 kernel headers. Anybody out there have a patch? The compile errors are below. set -e ; for i in memdisk dos win32 mtools unix extlinux sample com32 ; do make DATE=0x41e470ae HEXDATE=0x41e470ae -C $i all ; done make[1]: Entering directory `/usr/src/syslinux-3.07-pre1/memdisk' make[1]: Nothing to be done for `all'.

From: Wade Cline <clinew@linux.vnet.ibm.com> This patch is only an RFC. My internship is ending and I was hoping to get some feedback and incorporate any suggestions people may have before my internship ends along with life as we know it (this Friday). The filesystem should mount/umount properly but tends towards the explosive side when writes start happening. My current focus is on

Hello, Ok here are all my fsync changes, including the fix for the put_transaction stuff that I posted earlier. I figure it'll be easier to just commit it as one thing then each individual peice. The additional thing that I did was add a radix tree that tracks the current outstanding transactions. I also added a field to the in memory btrfs inode that keeps track of the last transaction

Hi Linus, Nick found a bad rb tree corruption problem in btrfs with fsx. It would be nice to have this in 2.6.31, so please pull. Thanks! git://git.kernel.dk/linux-2.6-block.git btrfs From: Nick Piggin (1): btrfs: fix inode rbtree corruption fs/btrfs/inode.c | 21 ++++++++++++++------- 1 files changed, 14 insertions(+), 7 deletions(-) diff --git a/fs/btrfs/inode.c

We''ve been keeping around the inode sequence number in hopes that somebody would use it, but nobody uses it and people actually use i_version which serves the same purpose, so use i_version where we used the incore inode''s sequence number and that way the sequence is updated properly across the board, and not just in file write. Thanks, Signed-off-by: Josef Bacik

Hello, I want to throw this out here now that I''ve got most of the heavy lifting done for this code to make sure what I''m doing is ok for now. I''ve added an ORPHAN_DIR item key to have a hidden dir per root. Right now it just does it for whatever the default root is on mount, but I''m going to fix that to do the orphan dir check/creation on lookup of a

A couple of years ago there was a discussion on lkml under the thread 'PATCH - ext2fs privacy (i.e. secure deletion) patch' about zapping deleted data in the filesystem as a security mechanism. The discussion wandered off into how 'chattr +s' could be implemented and whether encrypting filesystems wouldn't be a better solution to the problem. I've been maintaining a

Hello, I'd like to read superblock's information on Redhat 7.3, but I don't know how to do it. For example, Input : "/dev/sdj2" Output : ext2_super_block struct's s_wtime (I saw it at "/usr/include/ext2fs/ext2_fs.h") Input : "/dev/sdj1" Output : ext3_super_block struct's s_wtime (I saw it at