Re: [Next3-users] Kernel bug..
Brought to you by:
amir73il
Menu
▾
▴
Re: [Next3-users] Kernel bug..
|
From: Amir G. <ami...@gm...> - 2012-05-02 12:40:21
|
Follow the bread crumbs... check SNAPSHOT_VERSION inside linux-2.6.35.9/fs/next3/snapshot.h check SNAPSHOT_VERSION inside generated patch check SNAPSHOT_VERSION next3/snapshot.h in extracted patch after 'make module' On Wed, May 2, 2012 at 2:55 PM, Kim Hagen <kh...@mu...>wrote: > Hi Amir, > > I have rmmod the next3 module, then replaced the module with the new > compiled one, > than removed the initramfs and generated a new initramfs, than i rebooted. > > the output of next3 version: > snapshot-version = next3 snapshot v1.0.13-6 (2-May-2010) > > I do not understand why it is still v1.0.13-6, i am 100 percent sure i am > using the module i compiled with your steps! > > Kim. > > > > From: Amir Goldstein <ami...@gm...> > To: Kim Hagen <kh...@mu...>, > Cc: nex...@li... > Date: 05/02/2012 01:28 PM > Subject: Re: [Next3-users] Kernel bug.. > ------------------------------ > > > > Hi Kim, > > Nice work. > Can you please verify with command 'next3 version' that the latest code is > installed. > > Thanks, > Amir. > > On Wed, May 2, 2012 at 1:42 PM, Kim Hagen <*kh...@mu...*<kh...@mu...>> > wrote: > Hi Amir, > > I followed your guide, for the most part it is okay, > this is what i did: > 1. git clone git://*github.com/amir73il/next3-utils.git*<http://github.com/amir73il/next3-utils.git>-b next3-stable > That went ok. > > 2. git clone git://*github.com/amir73il/ext4-snapshots.git*<http://github.com/amir73il/ext4-snapshots.git>-b next3-stable ~/next3-utils/linux-2.6.35.9 > That gave the error: > Cloning into /root/next3-utils/linux-2.6.35.9... > fatal: remote error: access denied or repository not exported: > /0/nw/0f/29/37/17467/1022288.git > > I changed "git clone git://*github.com/amir73il/ext4-snapshots.git*<http://github.com/amir73il/ext4-snapshots.git>-b next3-stable ~/next3-utils/linux-2.6.35.9" > to " git clone https://*github.com/amir73il/ext4... etc"*<http://github.com/amir73il/ext4-snapshots.git> > than it downloaded the git. > > 3. I downloaded the tar ball from *kernel.org* <http://kernel.org/> i > hope that was the right place. > Make next3_snapshot went ok, and i copied the patch file to the correct > dir. > > on "make module" i get this error: > /root/next3-utils/next3/inode.c: In function ‘next3_write_begin’: > /root/next3-utils/next3/inode.c:1983: error: redeclaration of ‘page_bufs’ > with no linkage > /root/next3-utils/next3/inode.c:1981: error: previous declaration of > ‘page_bufs’ was here > make[4]: *** [/root/next3-utils/next3/inode.o] Error 1 > make[3]: *** [_module_/root/next3-utils/next3] Error 2 > make[2]: *** [sub-make] Error 2 > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-5-amd64' > make: *** [module] Error 2 > > so in inode.c i removed line 1983 "struct buffer_head *page_bufs;" because > it is double. > after that it compiles correct. > > sudo make test gives: > (test -f test.img && (./bin/tunefs.next3 -l test.img | grep UUID)) || \ > ( touch test.img ; ./bin/truncate -s 4G test.img ; yes | > ./bin/next3 mkfs test.img ) > /bin/sh: ./bin/truncate: not found > /bin/sh: ./bin/next3: Permission denied > make: *** [test] Error 126 > > so i did: > chmod +x ./bin/next3 > cp /sbin/tunefs.next3 /root/next3-utils/bin/ > gcc ./bin/truncate.c -o ./bin/truncate > ./bin/next3 config /dev/loop0 /root/next3-utils/test > > than i did a make test again, this time it was ok. > > I installed this module and tested for 2 days, but it crashed again with > the kernel bug. > there where no more errors on snapshot size... this is what i got: > > Apr 28 00:13:29 nl-gouda-07 kernel: *[14035.935096* <%5B14035.935096>] > snapshot: snapshot (40) created > Apr 28 00:13:29 nl-gouda-07 kernel: *[14036.117712* <%5B14036.117712>] > snapshot: snapshot (40) activated > Apr 28 00:13:29 nl-gouda-07 kernel: *[14036.119889* <%5B14036.119889>] > snapshot: snapshot (40) has been taken > Apr 28 00:18:56 nl-gouda-07 kernel: [14362.959709] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 00:19:33 nl-gouda-07 kernel: [14399.801548] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 00:19:34 nl-gouda-07 kernel: [14401.122780] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 00:27:52 nl-gouda-07 kernel: [14898.977055] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 00:37:58 nl-gouda-07 kernel: [15505.167611] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 00:48:05 nl-gouda-07 kernel: [16111.976134] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 00:58:02 nl-gouda-07 kernel: [16708.266859] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 01:01:02 nl-gouda-07 kernel: [16888.743711] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 01:06:57 nl-gouda-07 kernel: *[17243.999541* <%5B17243.999541>] > NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 > Apr 28 01:10:24 nl-gouda-07 kernel: [17450.672739] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 01:16:40 nl-gouda-07 kernel: [17826.835838] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 01:23:44 nl-gouda-07 kernel: [18250.445274] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 01:50:52 nl-gouda-07 kernel: [19878.965699] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 01:54:07 nl-gouda-07 kernel: [20073.717882] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 01:56:21 nl-gouda-07 kernel: [20207.764348] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 02:03:44 nl-gouda-07 kernel: [20651.138282] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 03:10:58 nl-gouda-07 kernel: [24684.735273] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 05:03:26 nl-gouda-07 kernel: [31432.762010] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 05:03:27 nl-gouda-07 kernel: [31433.424412] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 05:04:12 nl-gouda-07 kernel: [31478.818662] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 05:04:51 nl-gouda-07 kernel: [31518.054273] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 05:07:28 nl-gouda-07 kernel: [31674.387931] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 05:07:35 nl-gouda-07 kernel: [31681.206298] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 05:07:54 nl-gouda-07 kernel: [31700.680536] snapshot: > next3_snapshot_get_undo_access(b:0/67399) failed! h_ref=1, err=-5 > Apr 28 05:07:54 nl-gouda-07 kernel: [31700.680586] > next3_try_to_allocate_with_rsv: aborting transaction: IO failure in > __next3_journal_get_undo_access > Apr 28 05:07:54 nl-gouda-07 kernel: [31700.680636] NEXT3-fs error (device > dm-1) in next3_new_blocks: IO failure > Apr 28 05:07:54 nl-gouda-07 kernel: [31700.683029] NEXT3-fs error (device > dm-1) in next3_reserve_inode_write: Readonly filesystem > Apr 28 05:07:54 nl-gouda-07 kernel: [31700.686079] NEXT3-fs error (device > dm-1) in next3_dirty_inode: IO failure > Apr 28 05:07:54 nl-gouda-07 kernel: [31700.688997] NEXT3-fs error (device > dm-1) in next3_inode_list_add: Readonly filesystem > Apr 28 05:07:54 nl-gouda-07 kernel: [31700.691876] NEXT3-fs error (device > dm-1) in next3_write_begin: IO failure > Apr 28 05:07:54 nl-gouda-07 rsyncd[7886]: rsync: write failed on > "/de-duisburg-02/users/jriesen/Datenraum Upload/100114/Berlin/Karstadt > Berlin/Übergabe/PL_4_8_P91_K_Übergabe_1.OG_2009-02-02.pdf" (in BackupD$ > Apr 28 05:07:54 nl-gouda-07 rsyncd[7886]: rsync error: error in file IO > (code 11) at receiver.c(302) [receiver=3.0.7] > Apr 28 05:07:54 nl-gouda-07 kernel: [31700.796604] snapshot: > next3_snapshot_get_undo_access(b:0/67399) failed! h_ref=2, err=-5 > Apr 28 05:07:54 nl-gouda-07 kernel: [31700.796653] > __next3_free_blocks_sb_inode: aborting transaction: IO failure in > __next3_journal_get_undo_access > Apr 28 05:07:54 nl-gouda-07 kernel: [31700.796703] NEXT3-fs error (device > dm-1) in __next3_free_blocks_sb_inode: IO failure > Apr 28 05:07:54 nl-gouda-07 kernel: [31700.798835] NEXT3-fs error (device > dm-1) in next3_reserve_inode_write: Readonly filesystem > Apr 28 05:07:54 nl-gouda-07 kernel: [31700.800902] NEXT3-fs error (device > dm-1) in next3_truncate: IO failure > Apr 28 05:07:54 nl-gouda-07 kernel: [31700.802781] NEXT3-fs error (device > dm-1) in next3_reserve_inode_write: Readonly filesystem > Apr 28 05:07:54 nl-gouda-07 kernel: [31700.804680] NEXT3-fs error (device > dm-1) in next3_inode_list_del: Readonly filesystem > Apr 28 05:07:54 nl-gouda-07 kernel: [31700.806573] NEXT3-fs error (device > dm-1) in next3_reserve_inode_write: Readonly filesystem > Apr 28 05:07:54 nl-gouda-07 rsyncd[7886]: rsync: connection unexpectedly > closed (1491 bytes received so far) [generator] > Apr 28 05:07:54 nl-gouda-07 rsyncd[7886]: rsync error: error in rsync > protocol data stream (code 12) at io.c(601) [generator=3.0.7] > Apr 28 05:07:54 nl-gouda-07 kernel: [31700.808509] NEXT3-fs error (device > dm-1) in next3_delete_inode: IO failure > Apr 28 07:00:01 nl-gouda-07 kernel: [38428.065476] snapshot: snapshot (40) > enabled > Apr 28 07:00:02 nl-gouda-07 kernel: [38428.221302] EXT2-fs warning (device > loop0): ext2_fill_super: mounting ext3 filesystem as ext2 > Apr 28 07:00:02 nl-gouda-07 kernel: [38428.273634] snapshot: snapshot (41) > created > Apr 28 07:00:02 nl-gouda-07 kernel: [38428.496746] snapshot: snapshot (40) > deactivated > Apr 28 07:00:02 nl-gouda-07 kernel: [38428.496775] snapshot: snapshot (41) > activated > Apr 28 07:00:02 nl-gouda-07 kernel: [38428.499096] snapshot: snapshot (41) > has been taken > Apr 28 14:46:28 nl-gouda-07 kernel: [66414.369402] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 14:51:12 nl-gouda-07 kernel: [66699.008668] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 14:56:51 nl-gouda-07 kernel: [67038.132611] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 15:00:49 nl-gouda-07 kernel: [67275.861913] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 15:31:46 nl-gouda-07 kernel: [69132.992432] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 15:36:28 nl-gouda-07 kernel: [69414.349029] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 15:42:04 nl-gouda-07 kernel: [69750.628761] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 15:47:46 nl-gouda-07 kernel: [70092.838828] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 15:56:18 nl-gouda-07 kernel: [70604.857208] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 16:03:57 nl-gouda-07 kernel: [71063.811472] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 16:04:53 nl-gouda-07 kernel: [71119.524862] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 16:10:54 nl-gouda-07 kernel: [71481.129354] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.196616] snapshot: > next3_snapshot_get_undo_access(b:0/75613) failed! h_ref=1, err=-5 > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.196671] > next3_try_to_allocate_with_rsv: aborting transaction: IO failure in > __next3_journal_get_undo_access > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.196722] NEXT3-fs error (device > dm-1) in next3_new_blocks: IO failure > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.199043] NEXT3-fs error (device > dm-1) in next3_reserve_inode_write: Readonly filesystem > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.202149] NEXT3-fs error (device > dm-1) in next3_dirty_inode: IO failure > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.204081] NEXT3-fs error (device > dm-1) in next3_inode_list_add: Readonly filesystem > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.205988] NEXT3-fs error (device > dm-1) in next3_write_begin: IO failure > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.207894] snapshot: > next3_snapshot_get_undo_access(b:0/75613) failed! h_ref=1, err=-5 > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.207940] > next3_try_to_allocate_with_rsv: aborting transaction: IO failure in > __next3_journal_get_undo_access > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.207990] NEXT3-fs error (device > dm-1) in next3_new_blocks: IO failure > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.209874] NEXT3-fs error (device > dm-1) in next3_reserve_inode_write: Readonly filesystem > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.211735] NEXT3-fs error (device > dm-1) in next3_dirty_inode: IO failure > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.213615] NEXT3-fs error (device > dm-1) in next3_inode_list_add: Readonly filesystem > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.215481] NEXT3-fs error (device > dm-1) in next3_write_begin: IO failure > Apr 28 16:17:07 nl-gouda-07 rsyncd[7788]: rsync: write failed on > "/de-duisburg-02/collaboration/PR Material/08 P H O T O S/Multi > SPECIALS/Grundsteinlegung HI/DSC_0065.JPG" (in BackupData): Input/output > erro$ > Apr 28 16:17:07 nl-gouda-07 rsyncd[7788]: rsync error: error in file IO > (code 11) at receiver.c(302) [receiver=3.0.7] > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.320021] snapshot: > next3_snapshot_get_undo_access(b:0/75613) failed! h_ref=2, err=-5 > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.320069] > __next3_free_blocks_sb_inode: aborting transaction: IO failure in > __next3_journal_get_undo_access > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.320119] NEXT3-fs error (device > dm-1) in __next3_free_blocks_sb_inode: IO failure > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.322233] NEXT3-fs error (device > dm-1) in next3_reserve_inode_write: Readonly filesystem > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.324136] NEXT3-fs error (device > dm-1) in next3_truncate: IO failure > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.326013] NEXT3-fs error (device > dm-1) in next3_reserve_inode_write: Readonly filesystem > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.327881] NEXT3-fs error (device > dm-1) in next3_inode_list_del: Readonly filesystem > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.329767] NEXT3-fs error (device > dm-1) in next3_reserve_inode_write: Readonly filesystem > Apr 28 16:17:07 nl-gouda-07 kernel: [71853.331634] NEXT3-fs error (device > dm-1) in next3_delete_inode: IO failure > Apr 28 16:17:07 nl-gouda-07 rsyncd[7788]: rsync: connection unexpectedly > closed (318 bytes received so far) [generator] > Apr 28 16:17:07 nl-gouda-07 rsyncd[7788]: rsync error: error in rsync > protocol data stream (code 12) at io.c(601) [generator=3.0.7] > Apr 28 21:00:35 nl-gouda-07 kernel: [88861.295107] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 21:00:53 nl-gouda-07 kernel: [88880.080149] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 21:01:16 nl-gouda-07 kernel: [88902.539032] snapshot: > next3_snapshot_get_undo_access(b:0/75611) failed! h_ref=1, err=-5 > Apr 28 21:01:16 nl-gouda-07 kernel: [88902.539082] > next3_try_to_allocate_with_rsv: aborting transaction: IO failure in > __next3_journal_get_undo_access > Apr 28 21:01:16 nl-gouda-07 kernel: [88902.539132] NEXT3-fs error (device > dm-1) in next3_new_blocks: IO failure > Apr 28 21:01:16 nl-gouda-07 kernel: [88902.541587] NEXT3-fs error (device > dm-1) in next3_reserve_inode_write: Readonly filesystem > Apr 28 21:01:16 nl-gouda-07 kernel: [88902.543509] NEXT3-fs error (device > dm-1) in next3_dirty_inode: IO failure > Apr 28 21:01:16 nl-gouda-07 kernel: [88902.545632] NEXT3-fs error (device > dm-1) in next3_inode_list_add: Readonly filesystem > Apr 28 21:01:16 nl-gouda-07 kernel: [88902.547536] NEXT3-fs error (device > dm-1) in next3_write_begin: IO failure > Apr 28 21:01:16 nl-gouda-07 rsyncd[13398]: rsync: write failed on > "/de-duisburg-02/collaboration/PR Material/08 P H O T O S/Multi > SPECIALS/Grundsteinlegung HI/DSC_0065.JPG" (in BackupData): Input/output > err$ > Apr 28 21:01:16 nl-gouda-07 rsyncd[13398]: rsync error: error in file IO > (code 11) at receiver.c(302) [receiver=3.0.7] > Apr 28 21:01:16 nl-gouda-07 rsyncd[13398]: rsync: connection unexpectedly > closed (318 bytes received so far) [generator] > Apr 28 21:01:16 nl-gouda-07 rsyncd[13398]: rsync error: error in rsync > protocol data stream (code 12) at io.c(601) [generator=3.0.7] > Apr 28 21:01:40 nl-gouda-07 kernel: [88926.245689] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 21:01:49 nl-gouda-07 kernel: [88936.155510] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 22:00:13 nl-gouda-07 kernel: [92439.757287] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 22:54:50 nl-gouda-07 kernel: [95716.338122] snapshot: > next3_snapshot_get_undo_access(b:0/75611) failed! h_ref=1, err=-5 > Apr 28 22:54:50 nl-gouda-07 kernel: [95716.338172] > next3_try_to_allocate_with_rsv: aborting transaction: IO failure in > __next3_journal_get_undo_access > Apr 28 22:54:50 nl-gouda-07 kernel: [95716.338223] NEXT3-fs error (device > dm-1) in next3_new_blocks: IO failure > Apr 28 22:54:50 nl-gouda-07 kernel: [95716.340648] NEXT3-fs error (device > dm-1) in next3_reserve_inode_write: Readonly filesystem > Apr 28 22:54:50 nl-gouda-07 kernel: [95716.342592] NEXT3-fs error (device > dm-1) in next3_dirty_inode: IO failure > Apr 28 22:54:50 nl-gouda-07 kernel: [95716.344494] NEXT3-fs error (device > dm-1) in next3_inode_list_add: Readonly filesystem > Apr 28 22:54:50 nl-gouda-07 kernel: [95716.347113] NEXT3-fs error (device > dm-1) in next3_write_begin: IO failure > Apr 28 22:54:50 nl-gouda-07 rsyncd[2507]: rsync: write failed on > "/de-duisburg-02/collaboration/PR Material/08 P H O T O S/Multi > SPECIALS/Grundsteinlegung HI/DSC_0065.JPG" (in BackupData): Input/output > erro$ > Apr 28 22:54:50 nl-gouda-07 rsyncd[2507]: rsync error: error in file IO > (code 11) at receiver.c(302) [receiver=3.0.7] > Apr 28 22:54:50 nl-gouda-07 rsyncd[2507]: rsync: connection unexpectedly > closed (318 bytes received so far) [generator] > Apr 28 22:54:50 nl-gouda-07 rsyncd[2507]: rsync error: error in rsync > protocol data stream (code 12) at io.c(601) [generator=3.0.7] > Apr 28 22:55:20 nl-gouda-07 kernel: [95746.289565] snapshot: > next3_snapshot_get_undo_access(b:0/75611) failed! h_ref=1, err=-5 > Apr 28 22:55:20 nl-gouda-07 kernel: [95746.289615] > next3_try_to_allocate_with_rsv: aborting transaction: IO failure in > __next3_journal_get_undo_access > Apr 28 22:55:20 nl-gouda-07 kernel: [95746.289665] NEXT3-fs error (device > dm-1) in next3_new_blocks: IO failure > Apr 28 22:55:20 nl-gouda-07 kernel: [95746.298680] NEXT3-fs error (device > dm-1) in next3_reserve_inode_write: Readonly filesystem > Apr 28 22:55:20 nl-gouda-07 kernel: [95746.302063] NEXT3-fs error (device > dm-1) in next3_dirty_inode: IO failure > Apr 28 22:55:20 nl-gouda-07 kernel: [95746.305548] NEXT3-fs error (device > dm-1) in next3_inode_list_add: Readonly filesystem > Apr 28 22:55:20 nl-gouda-07 kernel: [95746.308946] NEXT3-fs error (device > dm-1) in next3_write_begin: IO failure > Apr 28 22:55:20 nl-gouda-07 rsyncd[2650]: rsync: write failed on > "/de-duisburg-02/collaboration/PR Material/08 P H O T O S/Multi > SPECIALS/Grundsteinlegung HI/DSC_0065.JPG" (in BackupData): Input/output > erro$ > Apr 28 22:55:20 nl-gouda-07 rsyncd[2650]: rsync error: error in file IO > (code 11) at receiver.c(302) [receiver=3.0.7] > Apr 28 22:55:20 nl-gouda-07 rsyncd[2650]: rsync: connection unexpectedly > closed (318 bytes received so far) [generator] > Apr 28 22:55:20 nl-gouda-07 rsyncd[2650]: rsync error: error in rsync > protocol data stream (code 12) at io.c(601) [generator=3.0.7] > Apr 28 22:55:20 nl-gouda-07 kernel: [95746.308946] NEXT3-fs error (device > dm-1) in next3_write_begin: IO failure > Apr 28 22:56:11 nl-gouda-07 kernel: [95797.407026] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 22:57:47 nl-gouda-07 kernel: [95893.235256] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 22:58:52 nl-gouda-07 kernel: [95958.314662] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 22:59:13 nl-gouda-07 kernel: [95979.615288] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 22:59:36 nl-gouda-07 kernel: [96002.961782] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 22:59:46 nl-gouda-07 kernel: [96012.318832] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 22:59:46 nl-gouda-07 kernel: [96012.491817] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 22:59:52 nl-gouda-07 kernel: [96018.871234] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.080469] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.080469] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115212] ------------[ cut here > ]------------ > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115242] kernel BUG at > /root/next3-utils/next3/snapshot.c:1063! > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115270] invalid opcode: 0000 > [#1] SMP > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115298] last sysfs file: > /sys/devices/pci0000:00/0000:00:04.0/0000:13:00.0/host4/port-4:0/end_device-4:0/target4:0:0/4:0:0:1/state > > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115351] CPU 0 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115373] Modules linked in: ext2 > next3 cpufreq_conservative cpufreq_powersave cpufreq_userspace > cpufreq_stats dm_round_robin dm_multipath scsi_dh loop radeon snd_pc$ > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115821] Pid: 2753, comm: rsync > Not tainted 2.6.32-5-amd64 #1 ProLiant DL380 G5 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115870] RIP: > 0010:[<ffffffffa0494335>] [<ffffffffa0494335>] > next3_snapshot_test_and_move+0x8b/0x264 [next3] > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115938] RSP: > 0018:ffff8801042d7888 EFLAGS: 00010202 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115965] RAX: ffff88007a511800 > RBX: 0000000000000000 RCX: 0000000000006a77 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115995] RDX: ffff880015385be8 > RSI: ffff88012f19fa98 RDI: ffffffffa049baf0 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116025] RBP: ffff880015385be8 > R08: 0000000000000001 R09: 0000000000000001 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116055] R10: 0000000000000004 > R11: 0000000000006a77 R12: 0000000000000001 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116084] R13: ffff88012f19fa98 > R14: ffff880015385be8 R15: 0000000000000001 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116115] FS: > 00007f57176b0700(0000) GS:ffff880005400000(0000) knlGS:0000000000000000 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116161] CS: 0010 DS: 0000 ES: > 0000 CR0: 000000008005003b > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116188] CR2: 00007f8e3ccc5000 > CR3: 000000012cfad000 CR4: 00000000000006f0 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116218] DR0: 0000000000000000 > DR1: 0000000000000000 DR2: 0000000000000000 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116248] DR3: 0000000000000000 > DR6: 00000000ffff0ff0 DR7: 0000000000000400 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116279] Process rsync (pid: > 2753, threadinfo ffff8801042d6000, task ffff88001731b170) > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116324] Stack: > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116344] ffffffff81065058 > 0000000000001000 0000000000006a77 ffffffffa049baf0 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116378] <0> ffff88007a514c00 > ffff8801042d79e8 0000000000000000 ffff880064984770 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116430] <0> ffff8801254428c0 > ffff8801042d79e8 ffff880015385be8 0000000000000004 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116497] Call Trace: > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116523] [<ffffffff81065058>] ? > wake_bit_function+0x0/0x23 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116555] [<ffffffffa0485cf3>] ? > next3_get_blocks_handle+0xc06/0x1127 [next3] > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116602] [<ffffffff810b8863>] ? > zone_watermark_ok+0x20/0xb1 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116634] [<ffffffffa04865f3>] ? > next3_getblk+0x53/0x172 [next3] > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116665] [<ffffffff8110da89>] ? > __find_get_block+0x176/0x186 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116696] [<ffffffffa0493d09>] ? > next3_snapshot_test_cow_bitmap+0x1e6/0x415 [next3] > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116745] [<ffffffffa01663c9>] ? > do_get_write_access+0x3e3/0x441 [jbd] > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116778] [<ffffffffa04947ba>] ? > next3_snapshot_test_and_cow+0x2ac/0x616 [next3] > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116827] [<ffffffffa0493336>] ? > __next3_journal_get_write_access_inode+0x40/0x8f [next3] > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116876] [<ffffffffa048233d>] ? > next3_new_inode+0x4f5/0x9f1 [next3] > Apr 28 23:02:43 nl-gouda-07 rsyncd[2735]: rsync: connection unexpectedly > closed (1491 bytes received so far) [generator] > Apr 28 23:02:43 nl-gouda-07 rsyncd[2735]: rsync error: error in rsync > protocol data stream (code 12) at io.c(601) [generator=3.0.7] > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116908] [<ffffffffa0166ba0>] ? > journal_start+0x96/0xc6 [jbd] > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116940] [<ffffffffa048b4a4>] ? > next3_create+0x96/0x113 [next3] > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116976] [<ffffffff810f6448>] ? > generic_permission+0xe/0x8a > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.117005] [<ffffffff810f7f44>] ? > vfs_create+0x6d/0x89 > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.117032] [<ffffffff810f8e6d>] ? > do_filp_open+0x31e/0x94b > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.117062] [<ffffffff810ed563>] ? > do_sys_open+0x55/0xfc > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.117090] [<ffffffff81010b42>] ? > system_call_fastpath+0x16/0x1b > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.117118] Code: 1e 44 89 0c 24 48 > 8b 54 24 20 45 31 c0 4c 8b 4c 24 10 48 8b 7c 24 18 48 89 e9 e8 02 f1 ff ff > 41 f6 45 14 08 75 05 4c 39 f5 75 04 <0f> 0b eb fe 4c 89 $ > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.117318] RIP > [<ffffffffa0494335>] next3_snapshot_test_and_move+0x8b/0x264 [next3] > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.117368] RSP <ffff8801042d7888> > Apr 28 23:02:43 nl-gouda-07 kernel: [96190.117643] ---[ end trace > 3f4f94f17ae3fc59 ]--- > > > > Kind regards, > > Kim > > > > > > > From: Amir Goldstein <*ami...@gm...* <ami...@gm...>> > To: Kim Hagen <*kh...@mu...*<kh...@mu...>>, > > Cc: *nex...@li...*<nex...@li...> > Date: 04/27/2012 08:34 PM > Subject: Re: [Next3-users] Kernel bug.. > ------------------------------ > > > > Hi Kim, > > ext4 snapshots is not available for kernel 2.6.32, only for kernel 2.6.38 > and above. > Also it is in a less stable state then next3. > So if you are going to use it for production, next3 is preferred. > ext4 snapshots would give you some performance benefits, since ext4 > performs better than ext3 > in several benchmarks. > > Regarding the next3 release, I need to refresh my memory, so I'll give you > initial pointers > and you can tell me what's missing. > > You will need to get (instructions assume you run this in your home dir): > > 1. The next3 utils: > ~$ git clone git://*github.com/amir73il/next3-utils.git*<http://github.com/amir73il/next3-utils.git>-b next3-stable > > 2. Linux tree with next3 sources. > The next3-stable branch is based off stable kernel 2.6.35.9, so check it > out like this: > ~$ git clone git://*github.com/amir73il/ext4-snapshots.git*<http://github.com/amir73il/ext4-snapshots.git>-b next3-stable ~/next3-utils/linux-2.6.35.9 > > 3. a tar ball of linux-2.6.35.9 and place it at: > ~/kernel/2.6.35/*linux-2.6.35.9.tar.bz* <http://linux-2.6.35.9.tar.bz/> > > Then run: > ~$ cd ~/next3-utils/patch > ~/next3-utils/patch$ make next3_snapshot > > This may take some time to unpack files from kernel tar ball and should > eventually create the patch file next3_snapshot.module.patch > and copy it to the ~/kernel/2.6.35/ dir. > > This is the same patch that is being downloaded from the web site for all > supported kernels (2.6.31-35). > If you copy it to ~/next3-util and run 'make module' in that directory, it > should build the latest next3 version > for your kernel (2.6.32), which you can test by running 'sudo make test'. > > I am pretty sure I missed something in the instructions, so please let me > know how far you got > and we'll take it from there. > > Thanks, > Amir. > > > On Fri, Apr 27, 2012 at 3:07 PM, Kim Hagen <*kh...@mu...*<kh...@mu...>> > wrote: > Hi Amir, > > I would like a walktrough please :), and what would you advice.... use > next3 or next3_ext4 (and if next3_ext4 how must i make my file-systen?) > > Kind regards, > > Kim > > > > > > > > This message contains information that may be priviliged or confidential > and is intended only for use by the addressee(s). > You are not authorized to use or distribute this message or any part of it > in any form, unless you are the intended recipient. > If you receive this communication unintentionally or in error, please > inform the sender immediately by return e-mail and delete all copies of > this message. > > If you do not want to receive any e-mail from Multi Corporation and/or its > affiliates in the future, please send an e-mail to: *no...@mu...*<no...@mu...> > Multi Corporation B.V., Gouda, is registered with the trade register in > the Netherlands under no. 34237857. > > > ------------------------------------------------------------------------------------------------------------------------------- > > Dit bericht bevat informatie die vertrouwelijk kan zijn en is uitsluitend > bestemd voor de geadresseerde(n). > Het is u niet toegestaan dit bericht of delen ervan te gebruiken of te > verspreiden in welke vorm dan ook, tenzij u de beoogde ontvanger bent. > Indien u dit bericht abusievelijk of onterecht ontvangt, wordt u verzocht > de afzender direkt te informeren door het bericht te retourneren en alle > kopieen van dit bericht direkt te verwijderen. > > Indien u geen email meer wilt ontvangen van Multi Corporation of haar > groepsvennootschappen kunt u dit kenbaar maken door een email te sturen > naar : *no...@mu...* <no...@mu...> > Multi Corporation B.V., Gouda, staat ingeschreven in de Kamer van > Koophandel onder nr. 34237857. > > > > > > > This message contains information that may be priviliged or confidential > and is intended only for use by the addressee(s). > You are not authorized to use or distribute this message or any part of it > in any form, unless you are the intended recipient. > If you receive this communication unintentionally or in error, please > inform the sender immediately by return e-mail and delete all copies of > this message. > > If you do not want to receive any e-mail from Multi Corporation and/or its > affiliates in the future, please send an e-mail to: no...@mu... > Multi Corporation B.V., Gouda, is registered with the trade register in > the Netherlands under no. 34237857. > > > ------------------------------------------------------------------------------------------------------------------------------- > > Dit bericht bevat informatie die vertrouwelijk kan zijn en is uitsluitend > bestemd voor de geadresseerde(n). > Het is u niet toegestaan dit bericht of delen ervan te gebruiken of te > verspreiden in welke vorm dan ook, tenzij u de beoogde ontvanger bent. > Indien u dit bericht abusievelijk of onterecht ontvangt, wordt u verzocht > de afzender direkt te informeren door het bericht te retourneren en alle > kopieen van dit bericht direkt te verwijderen. > > Indien u geen email meer wilt ontvangen van Multi Corporation of haar > groepsvennootschappen kunt u dit kenbaar maken door een email te sturen > naar : no...@mu... > Multi Corporation B.V., Gouda, staat ingeschreven in de Kamer van > Koophandel onder nr. 34237857. > |
