Re: [Next3-users] Kernel bug..
Brought to you by:
amir73il
Menu
▾
▴
Re: [Next3-users] Kernel bug..
|
From: Kim H. <kh...@mu...> - 2012-05-05 09:55:06
|
<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2">Hi Amir,<br><br>I could not get the clone of the stable branch so i downloaded each file individually<br>in the fs next3 folder :)<br><br>The build was without any problems, the module version now indeed is <font face="sans-serif">v1.0.13-8,<br>and is stable now for a few days, no error messages in dmesg and logs.<br><br>Thank you very much for your help.<br><br>Kind regards,<br><br>Kim Hagen<br></font><br><font color="#990099">-----Amir Goldstein <ami...@gm...> wrote: -----</font><div style="padding-left:5px;"><div style="padding-right:0px;padding-left:5px;border-left:solid black 2px;">To: Kim Hagen <kh...@mu...><br>From: Amir Goldstein <ami...@gm...><br>Date: 05/02/2012 04:03PM<br>Cc: nex...@li...<br>Subject: Re: [Next3-users] Kernel bug..<br><br><div dir="ltr"><div class="gmail_extra">Kim,</div><div class="gmail_extra"><br></div><div class="gmail_extra">I am not sure why clone -b doesn't work, and there is no need to grant read access,</div><div class="gmail_extra"> but if you manage to clone the repo, just checkout the next3-stable branch:</div><div class="gmail_extra"><br></div><div class="gmail_extra">cd ~/next3-utils/linux-2.6.35.9</div><div class="gmail_extra">git checkout -b next3-stable origin/next3-stable</div> <div class="gmail_extra"><br></div><div class="gmail_extra">Amir.<br><br><div class="gmail_quote">On Wed, May 2, 2012 at 4:56 PM, Kim Hagen <span dir="ltr"><<a href="mailto:kh...@mu..." target="_blank">kh...@mu...</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font face="sans-serif">Amir,</font> <br> <br><font face="sans-serif">Can you grant me access to clone branch?</font> <br><font face="sans-serif">or am i doing something wrong.</font> <br> <br><font face="sans-serif">root@nl-gouda-07:~# git clone -b next3-stable git://<a href="http://github.com/amir73il/ext4-snapshots.git" target="_blank">github.com/amir73il/ext4-snapshots.git</a> ~/next3-utils/linux-2.6.35.9</font> <br><div class="im"><font face="sans-serif">Cloning into /root/next3-utils/linux-2.6.35.9...</font> <br><font face="sans-serif">fatal: remote error: access denied or repository not exported: /0/nw/0f/29/37/17467/1022288.git</font> <br> <br></div><font face="sans-serif">Kim</font> <br> <br> <br> <br><font color="#5f5f5f" face="sans-serif" size="1">From: </font><font face="sans-serif" size="1">Kim Hagen <<a href="mailto:kh...@mu..." target="_blank">kh...@mu...</a>></font> <br><font color="#5f5f5f" face="sans-serif" size="1">To: </font><font face="sans-serif" size="1">Amir Goldstein <<a href="mailto:ami...@gm..." target="_blank">ami...@gm...</a>>, </font> <br><font color="#5f5f5f" face="sans-serif" size="1">Cc: </font><font face="sans-serif" size="1"><a href="mailto:nex...@li..." target="_blank">nex...@li...</a></font> <br><font color="#5f5f5f" face="sans-serif" size="1">Date: </font><font face="sans-serif" size="1">05/02/2012 03:03 PM</font> <br><div><div class="h5"><font color="#5f5f5f" face="sans-serif" size="1">Subject: </font><font face="sans-serif" size="1">Re: [Next3-users] Kernel bug..</font> <br> <hr noshade="noshade"> <br> <br> <br><font face="sans-serif">Hi Amir,</font><font size="3"> <br> </font><font face="sans-serif"><br> Ok, the outcome:</font><font size="3"> </font><font face="sans-serif"><br> /root/next3-utils/linux-2.6.35.9/fs/next3/snapshot.h #define NEXT3_SNAPSHOT_VERSION "next3 snapshot v1.0.13-6 (2-May-2010)"</font><font size="3"> <br> inside generated patch</font><font face="sans-serif"> +#define NEXT3_SNAPSHOT_VERSION "next3 snapshot v1.0.13-6 (2-May-2010)"</font><font size="3"> <br> next3/snapshot.h</font><font face="sans-serif"> #define NEXT3_SNAPSHOT_VERSION "next3 snapshot v1.0.13-6 (2-May-2010)"</font><font size="3"> <br> </font><font face="sans-serif"><br> In </font><a href="https://github.com/amir73il/ext4-snapshots/blob/ext4-snapshots/fs/next3/snapshot.h" target="_blank"><font color="blue" face="sans-serif"><u>https://github.com/amir73il/ext4-snapshots/blob/ext4-snapshots/fs/next3/snapshot.h</u></font></a><font size="3"> </font><font face="sans-serif"><br> the version is also "next3 snapshot v1.0.13-6 (2-May-2010)".</font><font size="3"> <br> </font><font face="sans-serif"><br> I think i got the wrong branch with the git clone, i see the stable with version </font><tt><font face="Courier New,Courier,monospace" size="2">"next3 snapshot v1.0.13-8 (2-Aug-2011)"</font></tt><font face="sans-serif"> I will try the correct branch and let you know.</font><font size="3"> <br> </font><font face="sans-serif"><br> Kind regards, </font><font size="3"><br> </font><font face="sans-serif"><br> Kim</font><font size="3"> <br> <br> <br> </font><font color="#5f5f5f" face="sans-serif" size="1"><br> From: </font><font face="sans-serif" size="1">Amir Goldstein <<a href="mailto:ami...@gm..." target="_blank">ami...@gm...</a>></font><font size="3"> </font><font color="#5f5f5f" face="sans-serif" size="1"><br> To: </font><font face="sans-serif" size="1">Kim Hagen <<a href="mailto:kh...@mu..." target="_blank">kh...@mu...</a>>, </font><font color="#5f5f5f" face="sans-serif" size="1"><br> Cc: </font><font face="sans-serif" size="1"><a href="mailto:nex...@li..." target="_blank">nex...@li...</a></font><font size="3"> </font><font color="#5f5f5f" face="sans-serif" size="1"><br> Date: </font><font face="sans-serif" size="1">05/02/2012 02:40 PM</font><font size="3"> </font><font color="#5f5f5f" face="sans-serif" size="1"><br> Subject: </font><font face="sans-serif" size="1">Re: [Next3-users] Kernel bug..</font><font size="3"> <br> </font> <hr noshade="noshade"><font size="3"><br> <br> <br> Follow the bread crumbs... <br> check SNAPSHOT_VERSION inside linux-2.6.35.9/fs/next3/snapshot.h <br> check SNAPSHOT_VERSION inside generated patch<br> check SNAPSHOT_VERSION next3/snapshot.h in extracted patch after 'make module' <br> <br> On Wed, May 2, 2012 at 2:55 PM, Kim Hagen <</font><a href="mailto:kh...@mu..." target="_blank"><font color="blue" size="3"><u>kh...@mu...</u></font></a><font size="3">> wrote: </font><font face="sans-serif" size="3"><br> Hi Amir,</font><font size="3"> </font><font face="sans-serif" size="3"><br> <br> I have rmmod the next3 module, then replaced the module with the new compiled one, <br> than removed the initramfs and generated a new initramfs, than i rebooted.</font><font size="3"> </font><font face="sans-serif" size="3"><br> <br> the output of next3 version:</font><font size="3"> </font><font face="sans-serif" size="3"><br> snapshot-version = next3 snapshot v1.0.13-6 (2-May-2010)</font><font size="3"> <br> </font><font face="sans-serif" size="3"><br> 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!</font><font size="3"> </font><font face="sans-serif" size="3"><br> <br> Kim.</font><font size="3"> <br> <br> </font><font color="#5f5f5f" face="sans-serif" size="1"><br> <br> From: </font><font face="sans-serif" size="1">Amir Goldstein <</font><a href="mailto:ami...@gm..." target="_blank"><font color="blue" face="sans-serif" size="1"><u>ami...@gm...</u></font></a><font face="sans-serif" size="1">></font><font size="3"> </font><font color="#5f5f5f" face="sans-serif" size="1"><br> To: </font><font face="sans-serif" size="1">Kim Hagen <</font><a href="mailto:kh...@mu..." target="_blank"><font color="blue" face="sans-serif" size="1"><u>kh...@mu...</u></font></a><font face="sans-serif" size="1">>, </font><font color="#5f5f5f" face="sans-serif" size="1"><br> Cc: </font><a href="mailto:nex...@li..." target="_blank"><font color="blue" face="sans-serif" size="1"><u>nex...@li...</u></font></a><font size="3"> </font><font color="#5f5f5f" face="sans-serif" size="1"><br> Date: </font><font face="sans-serif" size="1">05/02/2012 01:28 PM</font><font size="3"> </font><font color="#5f5f5f" face="sans-serif" size="1"><br> Subject: </font><font face="sans-serif" size="1">Re: [Next3-users] Kernel bug..</font><font size="3"> <br> </font> <hr noshade="noshade"><font size="3"><br> <br> <br> Hi Kim, <br> <br> Nice work. <br> Can you please verify with command 'next3 version' that the latest code is installed. <br> <br> Thanks, <br> Amir.<br> <br> On Wed, May 2, 2012 at 1:42 PM, Kim Hagen <</font><a href="mailto:kh...@mu..." target="_blank"><font color="blue" size="3"><u>kh...@mu...</u></font></a><font size="3">> wrote: </font><font face="sans-serif" size="3"><br> Hi Amir,</font><font size="3"> </font><font face="sans-serif" size="3"><br> <br> I followed your guide, for the most part it is okay,</font><font size="3"> </font><font face="sans-serif" size="3"><br> this is what i did:</font><font size="3"> </font><font face="sans-serif" size="3"><br> 1. </font><font size="3">git clone git://</font><a href="http://github.com/amir73il/next3-utils.git" target="_blank"><font color="blue" size="3"><u>github.com/amir73il/next3-utils.git</u></font></a><font size="3"> -b next3-stable </font><font face="sans-serif" size="3"><br> That went ok.</font><font size="3"> </font><font face="sans-serif" size="3"><br> <br> 2. </font><font size="3">git clone git://</font><a href="http://github.com/amir73il/ext4-snapshots.git" target="_blank"><font color="blue" size="3"><u>github.com/amir73il/ext4-snapshots.git</u></font></a><font size="3"> -b next3-stable ~/next3-utils/linux-2.6.35.9 </font><font face="sans-serif" size="3"><br> That gave the error:</font><font size="3"> <br> Cloning into /root/next3-utils/linux-2.6.35.9... <br> fatal: remote error: access denied or repository not exported: /0/nw/0f/29/37/17467/1022288.git </font><font face="sans-serif" size="3"><br> <br> I changed "</font><font size="3">git clone git://</font><a href="http://github.com/amir73il/ext4-snapshots.git" target="_blank"><font color="blue" size="3"><u>github.com/amir73il/ext4-snapshots.git</u></font></a><font size="3"> -b next3-stable ~/next3-utils/linux-2.6.35.9</font><font face="sans-serif" size="3">" to " </font><font size="3">git clone https://</font><a href="http://github.com/amir73il/ext4-snapshots.git" target="_blank"><font color="blue" size="3"><u>github.com/amir73il/ext4... etc"</u></font></a><font size="3"> </font><font face="sans-serif" size="3"><br> than it downloaded the git.</font><font size="3"> </font><font face="sans-serif" size="3"><br> <br> 3. I downloaded the tar ball from </font><a href="http://kernel.org/" target="_blank"><font color="blue" face="sans-serif" size="3"><u>kernel.org</u></font></a><font face="sans-serif" size="3"> i hope that was the right place.</font><font size="3"> <br> Make next3_snapshot</font><font face="sans-serif" size="3"> went ok, and i copied the patch file to the correct dir.</font><font size="3"> </font><font face="sans-serif" size="3"><br> <br> on "make module" i get this error:</font><font size="3"> <br> /root/next3-utils/next3/inode.c: In function ‘next3_write_begin’: <br> /root/next3-utils/next3/inode.c:1983: error: redeclaration of ‘page_bufs’ with no linkage <br> /root/next3-utils/next3/inode.c:1981: error: previous declaration of ‘page_bufs’ was here <br> make[4]: *** [/root/next3-utils/next3/inode.o] Error 1 <br> make[3]: *** [_module_/root/next3-utils/next3] Error 2 <br> make[2]: *** [sub-make] Error 2 <br> make[1]: *** [all] Error 2 <br> make[1]: Leaving directory `/usr/src/linux-headers-2.6.32-5-amd64' <br> make: *** [module] Error 2 </font><font face="sans-serif" size="3"><br> <br> so in inode.c i removed line 1983 "struct buffer_head *page_bufs;" because it is double.</font><font size="3"> </font><font face="sans-serif" size="3"><br> after that it compiles correct.</font><font size="3"> </font><font face="sans-serif" size="3"><br> <br> sudo make test gives:</font><font size="3"> <br> (test -f test.img && (./bin/tunefs.next3 -l test.img | grep UUID)) || \ <br> ( touch test.img ; ./bin/truncate -s 4G test.img ; yes | ./bin/next3 mkfs test.img ) <br> /bin/sh: ./bin/truncate: not found <br> /bin/sh: ./bin/next3: Permission denied <br> make: *** [test] Error 126 </font><font face="sans-serif" size="3"><br> <br> so i did:</font><font size="3"> <br> chmod +x ./bin/next3 <br> cp /sbin/tunefs.next3 /root/next3-utils/bin/ <br> gcc ./bin/truncate.c -o ./bin/truncate <br> ./bin/next3 config /dev/loop0 /root/next3-utils/test </font><font face="sans-serif" size="3"><br> <br> than i did a make test again, this time it was ok.</font><font size="3"> </font><font face="sans-serif" size="3"><br> <br> I installed this module and tested for 2 days, but it crashed again with the kernel bug.</font><font size="3"> </font><font face="sans-serif" size="3"><br> there where no more errors on snapshot size... this is what i got:</font><font size="3"> <br> <br> Apr 28 00:13:29 nl-gouda-07 kernel: </font><a href="tel:%5B14035.935096" target="_blank"><font color="blue" size="3"><u>[14035.935096</u></font></a><font size="3">] snapshot: snapshot (40) created <br> Apr 28 00:13:29 nl-gouda-07 kernel: </font><a href="tel:%5B14036.117712" target="_blank"><font color="blue" size="3"><u>[14036.117712</u></font></a><font size="3">] snapshot: snapshot (40) activated <br> Apr 28 00:13:29 nl-gouda-07 kernel: </font><a href="tel:%5B14036.119889" target="_blank"><font color="blue" size="3"><u>[14036.119889</u></font></a><font size="3">] snapshot: snapshot (40) has been taken <br> Apr 28 00:18:56 nl-gouda-07 kernel: [14362.959709] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 00:19:33 nl-gouda-07 kernel: [14399.801548] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 00:19:34 nl-gouda-07 kernel: [14401.122780] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 00:27:52 nl-gouda-07 kernel: [14898.977055] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 00:37:58 nl-gouda-07 kernel: [15505.167611] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 00:48:05 nl-gouda-07 kernel: [16111.976134] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 00:58:02 nl-gouda-07 kernel: [16708.266859] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 01:01:02 nl-gouda-07 kernel: [16888.743711] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 01:06:57 nl-gouda-07 kernel: </font><a href="tel:%5B17243.999541" target="_blank"><font color="blue" size="3"><u>[17243.999541</u></font></a><font size="3">] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 01:10:24 nl-gouda-07 kernel: [17450.672739] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 01:16:40 nl-gouda-07 kernel: [17826.835838] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 01:23:44 nl-gouda-07 kernel: [18250.445274] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 01:50:52 nl-gouda-07 kernel: [19878.965699] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 01:54:07 nl-gouda-07 kernel: [20073.717882] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 01:56:21 nl-gouda-07 kernel: [20207.764348] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 02:03:44 nl-gouda-07 kernel: [20651.138282] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 03:10:58 nl-gouda-07 kernel: [24684.735273] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 05:03:26 nl-gouda-07 kernel: [31432.762010] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 05:03:27 nl-gouda-07 kernel: [31433.424412] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 05:04:12 nl-gouda-07 kernel: [31478.818662] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 05:04:51 nl-gouda-07 kernel: [31518.054273] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 05:07:28 nl-gouda-07 kernel: [31674.387931] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 05:07:35 nl-gouda-07 kernel: [31681.206298] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> 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 <br> 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 <br> Apr 28 05:07:54 nl-gouda-07 kernel: [31700.680636] NEXT3-fs error (device dm-1) in next3_new_blocks: IO failure <br> Apr 28 05:07:54 nl-gouda-07 kernel: [31700.683029] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem <br> Apr 28 05:07:54 nl-gouda-07 kernel: [31700.686079] NEXT3-fs error (device dm-1) in next3_dirty_inode: IO failure <br> Apr 28 05:07:54 nl-gouda-07 kernel: [31700.688997] NEXT3-fs error (device dm-1) in next3_inode_list_add: Readonly filesystem <br> Apr 28 05:07:54 nl-gouda-07 kernel: [31700.691876] NEXT3-fs error (device dm-1) in next3_write_begin: IO failure <br> 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$ <br> 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] <br> 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 <br> 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 <br> 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 <br> Apr 28 05:07:54 nl-gouda-07 kernel: [31700.798835] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem <br> Apr 28 05:07:54 nl-gouda-07 kernel: [31700.800902] NEXT3-fs error (device dm-1) in next3_truncate: IO failure <br> Apr 28 05:07:54 nl-gouda-07 kernel: [31700.802781] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem <br> Apr 28 05:07:54 nl-gouda-07 kernel: [31700.804680] NEXT3-fs error (device dm-1) in next3_inode_list_del: Readonly filesystem <br> Apr 28 05:07:54 nl-gouda-07 kernel: [31700.806573] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem <br> Apr 28 05:07:54 nl-gouda-07 rsyncd[7886]: rsync: connection unexpectedly closed (1491 bytes received so far) [generator] <br> 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] <br> Apr 28 05:07:54 nl-gouda-07 kernel: [31700.808509] NEXT3-fs error (device dm-1) in next3_delete_inode: IO failure <br> Apr 28 07:00:01 nl-gouda-07 kernel: [38428.065476] snapshot: snapshot (40) enabled <br> Apr 28 07:00:02 nl-gouda-07 kernel: [38428.221302] EXT2-fs warning (device loop0): ext2_fill_super: mounting ext3 filesystem as ext2 <br> Apr 28 07:00:02 nl-gouda-07 kernel: [38428.273634] snapshot: snapshot (41) created <br> Apr 28 07:00:02 nl-gouda-07 kernel: [38428.496746] snapshot: snapshot (40) deactivated <br> Apr 28 07:00:02 nl-gouda-07 kernel: [38428.496775] snapshot: snapshot (41) activated <br> Apr 28 07:00:02 nl-gouda-07 kernel: [38428.499096] snapshot: snapshot (41) has been taken <br> Apr 28 14:46:28 nl-gouda-07 kernel: [66414.369402] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 14:51:12 nl-gouda-07 kernel: [66699.008668] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 14:56:51 nl-gouda-07 kernel: [67038.132611] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 15:00:49 nl-gouda-07 kernel: [67275.861913] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 15:31:46 nl-gouda-07 kernel: [69132.992432] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 15:36:28 nl-gouda-07 kernel: [69414.349029] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 15:42:04 nl-gouda-07 kernel: [69750.628761] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 15:47:46 nl-gouda-07 kernel: [70092.838828] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 15:56:18 nl-gouda-07 kernel: [70604.857208] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 16:03:57 nl-gouda-07 kernel: [71063.811472] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 16:04:53 nl-gouda-07 kernel: [71119.524862] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 16:10:54 nl-gouda-07 kernel: [71481.129354] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> 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 <br> 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 <br> Apr 28 16:17:07 nl-gouda-07 kernel: [71853.196722] NEXT3-fs error (device dm-1) in next3_new_blocks: IO failure <br> Apr 28 16:17:07 nl-gouda-07 kernel: [71853.199043] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem <br> Apr 28 16:17:07 nl-gouda-07 kernel: [71853.202149] NEXT3-fs error (device dm-1) in next3_dirty_inode: IO failure <br> Apr 28 16:17:07 nl-gouda-07 kernel: [71853.204081] NEXT3-fs error (device dm-1) in next3_inode_list_add: Readonly filesystem <br> Apr 28 16:17:07 nl-gouda-07 kernel: [71853.205988] NEXT3-fs error (device dm-1) in next3_write_begin: IO failure <br> 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 <br> 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 <br> Apr 28 16:17:07 nl-gouda-07 kernel: [71853.207990] NEXT3-fs error (device dm-1) in next3_new_blocks: IO failure <br> Apr 28 16:17:07 nl-gouda-07 kernel: [71853.209874] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem <br> Apr 28 16:17:07 nl-gouda-07 kernel: [71853.211735] NEXT3-fs error (device dm-1) in next3_dirty_inode: IO failure <br> Apr 28 16:17:07 nl-gouda-07 kernel: [71853.213615] NEXT3-fs error (device dm-1) in next3_inode_list_add: Readonly filesystem <br> Apr 28 16:17:07 nl-gouda-07 kernel: [71853.215481] NEXT3-fs error (device dm-1) in next3_write_begin: IO failure <br> 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$ <br> 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] <br> 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 <br> 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 <br> 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 <br> Apr 28 16:17:07 nl-gouda-07 kernel: [71853.322233] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem <br> Apr 28 16:17:07 nl-gouda-07 kernel: [71853.324136] NEXT3-fs error (device dm-1) in next3_truncate: IO failure <br> Apr 28 16:17:07 nl-gouda-07 kernel: [71853.326013] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem <br> Apr 28 16:17:07 nl-gouda-07 kernel: [71853.327881] NEXT3-fs error (device dm-1) in next3_inode_list_del: Readonly filesystem <br> Apr 28 16:17:07 nl-gouda-07 kernel: [71853.329767] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem <br> Apr 28 16:17:07 nl-gouda-07 kernel: [71853.331634] NEXT3-fs error (device dm-1) in next3_delete_inode: IO failure <br> Apr 28 16:17:07 nl-gouda-07 rsyncd[7788]: rsync: connection unexpectedly closed (318 bytes received so far) [generator] <br> 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] <br> Apr 28 21:00:35 nl-gouda-07 kernel: [88861.295107] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 21:00:53 nl-gouda-07 kernel: [88880.080149] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> 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 <br> 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 <br> Apr 28 21:01:16 nl-gouda-07 kernel: [88902.539132] NEXT3-fs error (device dm-1) in next3_new_blocks: IO failure <br> Apr 28 21:01:16 nl-gouda-07 kernel: [88902.541587] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem <br> Apr 28 21:01:16 nl-gouda-07 kernel: [88902.543509] NEXT3-fs error (device dm-1) in next3_dirty_inode: IO failure <br> Apr 28 21:01:16 nl-gouda-07 kernel: [88902.545632] NEXT3-fs error (device dm-1) in next3_inode_list_add: Readonly filesystem <br> Apr 28 21:01:16 nl-gouda-07 kernel: [88902.547536] NEXT3-fs error (device dm-1) in next3_write_begin: IO failure <br> 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$ <br> 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] <br> Apr 28 21:01:16 nl-gouda-07 rsyncd[13398]: rsync: connection unexpectedly closed (318 bytes received so far) [generator] <br> 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] <br> Apr 28 21:01:40 nl-gouda-07 kernel: [88926.245689] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 21:01:49 nl-gouda-07 kernel: [88936.155510] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 22:00:13 nl-gouda-07 kernel: [92439.757287] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> 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 <br> 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 <br> Apr 28 22:54:50 nl-gouda-07 kernel: [95716.338223] NEXT3-fs error (device dm-1) in next3_new_blocks: IO failure <br> Apr 28 22:54:50 nl-gouda-07 kernel: [95716.340648] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem <br> Apr 28 22:54:50 nl-gouda-07 kernel: [95716.342592] NEXT3-fs error (device dm-1) in next3_dirty_inode: IO failure <br> Apr 28 22:54:50 nl-gouda-07 kernel: [95716.344494] NEXT3-fs error (device dm-1) in next3_inode_list_add: Readonly filesystem <br> Apr 28 22:54:50 nl-gouda-07 kernel: [95716.347113] NEXT3-fs error (device dm-1) in next3_write_begin: IO failure <br> 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$ <br> 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] <br> Apr 28 22:54:50 nl-gouda-07 rsyncd[2507]: rsync: connection unexpectedly closed (318 bytes received so far) [generator] <br> 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] <br> 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 <br> 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 <br> Apr 28 22:55:20 nl-gouda-07 kernel: [95746.289665] NEXT3-fs error (device dm-1) in next3_new_blocks: IO failure <br> Apr 28 22:55:20 nl-gouda-07 kernel: [95746.298680] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem <br> Apr 28 22:55:20 nl-gouda-07 kernel: [95746.302063] NEXT3-fs error (device dm-1) in next3_dirty_inode: IO failure <br> Apr 28 22:55:20 nl-gouda-07 kernel: [95746.305548] NEXT3-fs error (device dm-1) in next3_inode_list_add: Readonly filesystem <br> Apr 28 22:55:20 nl-gouda-07 kernel: [95746.308946] NEXT3-fs error (device dm-1) in next3_write_begin: IO failure <br> 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$ <br> 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] <br> Apr 28 22:55:20 nl-gouda-07 rsyncd[2650]: rsync: connection unexpectedly closed (318 bytes received so far) [generator] <br> 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] <br> Apr 28 22:55:20 nl-gouda-07 kernel: [95746.308946] NEXT3-fs error (device dm-1) in next3_write_begin: IO failure <br> Apr 28 22:56:11 nl-gouda-07 kernel: [95797.407026] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 22:57:47 nl-gouda-07 kernel: [95893.235256] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 22:58:52 nl-gouda-07 kernel: [95958.314662] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 22:59:13 nl-gouda-07 kernel: [95979.615288] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 22:59:36 nl-gouda-07 kernel: [96002.961782] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 22:59:46 nl-gouda-07 kernel: [96012.318832] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 22:59:46 nl-gouda-07 kernel: [96012.491817] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 22:59:52 nl-gouda-07 kernel: [96018.871234] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.080469] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.080469] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115212] ------------[ cut here ]------------ <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115242] kernel BUG at /root/next3-utils/next3/snapshot.c:1063! <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115270] invalid opcode: 0000 [#1] SMP <br> 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 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115351] CPU 0 <br> 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$ <br> 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 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115870] RIP: 0010:[<ffffffffa0494335>] [<ffffffffa0494335>] next3_snapshot_test_and_move+0x8b/0x264 [next3] <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115938] RSP: 0018:ffff8801042d7888 EFLAGS: 00010202 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115965] RAX: ffff88007a511800 RBX: 0000000000000000 RCX: 0000000000006a77 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.115995] RDX: ffff880015385be8 RSI: ffff88012f19fa98 RDI: ffffffffa049baf0 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116025] RBP: ffff880015385be8 R08: 0000000000000001 R09: 0000000000000001 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116055] R10: 0000000000000004 R11: 0000000000006a77 R12: 0000000000000001 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116084] R13: ffff88012f19fa98 R14: ffff880015385be8 R15: 0000000000000001 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116115] FS: 00007f57176b0700(0000) GS:ffff880005400000(0000) knlGS:0000000000000000 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116161] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116188] CR2: 00007f8e3ccc5000 CR3: 000000012cfad000 CR4: 00000000000006f0 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116218] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116248] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116279] Process rsync (pid: 2753, threadinfo ffff8801042d6000, task ffff88001731b170) <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116324] Stack: <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116344] ffffffff81065058 0000000000001000 0000000000006a77 ffffffffa049baf0 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116378] <0> ffff88007a514c00 ffff8801042d79e8 0000000000000000 ffff880064984770 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116430] <0> ffff8801254428c0 ffff8801042d79e8 ffff880015385be8 0000000000000004 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116497] Call Trace: <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116523] [<ffffffff81065058>] ? wake_bit_function+0x0/0x23 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116555] [<ffffffffa0485cf3>] ? next3_get_blocks_handle+0xc06/0x1127 [next3] <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116602] [<ffffffff810b8863>] ? zone_watermark_ok+0x20/0xb1 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116634] [<ffffffffa04865f3>] ? next3_getblk+0x53/0x172 [next3] <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116665] [<ffffffff8110da89>] ? __find_get_block+0x176/0x186 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116696] [<ffffffffa0493d09>] ? next3_snapshot_test_cow_bitmap+0x1e6/0x415 [next3] <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116745] [<ffffffffa01663c9>] ? do_get_write_access+0x3e3/0x441 [jbd] <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116778] [<ffffffffa04947ba>] ? next3_snapshot_test_and_cow+0x2ac/0x616 [next3] <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116827] [<ffffffffa0493336>] ? __next3_journal_get_write_access_inode+0x40/0x8f [next3] <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116876] [<ffffffffa048233d>] ? next3_new_inode+0x4f5/0x9f1 [next3] <br> Apr 28 23:02:43 nl-gouda-07 rsyncd[2735]: rsync: connection unexpectedly closed (1491 bytes received so far) [generator] <br> 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] <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116908] [<ffffffffa0166ba0>] ? journal_start+0x96/0xc6 [jbd] <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116940] [<ffffffffa048b4a4>] ? next3_create+0x96/0x113 [next3] <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.116976] [<ffffffff810f6448>] ? generic_permission+0xe/0x8a <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.117005] [<ffffffff810f7f44>] ? vfs_create+0x6d/0x89 <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.117032] [<ffffffff810f8e6d>] ? do_filp_open+0x31e/0x94b <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.117062] [<ffffffff810ed563>] ? do_sys_open+0x55/0xfc <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.117090] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b <br> 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 $ <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.117318] RIP [<ffffffffa0494335>] next3_snapshot_test_and_move+0x8b/0x264 [next3] <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.117368] RSP <ffff8801042d7888> <br> Apr 28 23:02:43 nl-gouda-07 kernel: [96190.117643] ---[ end trace 3f4f94f17ae3fc59 ]--- <br> </font><font face="sans-serif" size="3"><br> <br> <br> Kind regards,</font><font size="3"> </font><font face="sans-serif" size="3"><br> <br> Kim</font><font size="3"> <br> <br> <br> <br> </font><font color="#5f5f5f" face="sans-serif" size="1"><br> <br> <br> From: </font><font face="sans-serif" size="1">Amir Goldstein <</font><a href="mailto:ami...@gm..." target="_blank"><font color="blue" face="sans-serif" size="1"><u>ami...@gm...</u></font></a><font face="sans-serif" size="1">></font><font size="3"> </font><font color="#5f5f5f" face="sans-serif" size="1"><br> To: </font><font face="sans-serif" size="1">Kim Hagen <</font><a href="mailto:kh...@mu..." target="_blank"><font color="blue" face="sans-serif" size="1"><u>kh...@mu...</u></font></a><font face="sans-serif" size="1">>, </font><font color="#5f5f5f" face="sans-serif" size="1"><br> Cc: </font><a href="mailto:nex...@li..." target="_blank"><font color="blue" face="sans-serif" size="1"><u>nex...@li...</u></font></a><font size="3"> </font><font color="#5f5f5f" face="sans-serif" size="1"><br> Date: </font><font face="sans-serif" size="1">04/27/2012 08:34 PM</font><font size="3"> </font><font color="#5f5f5f" face="sans-serif" size="1"><br> Subject: </font><font face="sans-serif" size="1">Re: [Next3-users] Kernel bug..</font><font size="3"> <br> </font> <hr noshade="noshade"><font size="3"><br> <br> <br> Hi Kim, <br> <br> ext4 snapshots is not available for kernel 2.6.32, only for kernel 2.6.38 and above. <br> Also it is in a less stable state then next3. <br> So if you are going to use it for production, next3 is preferred. <br> ext4 snapshots would give you some performance benefits, since ext4 performs better than ext3 <br> in several benchmarks. <br> <br> Regarding the next3 release, I need to refresh my memory, so I'll give you initial pointers <br> and you can tell me what's missing. <br> <br> You will need to get (instructions assume you run this in your home dir): <br> <br> 1. The next3 utils: <br> ~$ git clone git://</font><a href="http://github.com/amir73il/next3-utils.git" target="_blank"><font color="blue" size="3"><u>github.com/amir73il/next3-utils.git</u></font></a><font size="3"> -b next3-stable <br> <br> 2. Linux tree with next3 sources. <br> The next3-stable branch is based off stable kernel 2.6.35.9, so check it out like this: <br> ~$ git clone git://</font><a href="http://github.com/amir73il/ext4-snapshots.git" target="_blank"><font color="blue" size="3"><u>github.com/amir73il/ext4-snapshots.git</u></font></a><font size="3"> -b next3-stable ~/next3-utils/linux-2.6.35.9 <br> <br> 3. a tar ball of linux-2.6.35.9 and place it at: <br> ~/kernel/2.6.35/</font><a href="http://linux-2.6.35.9.tar.bz/" target="_blank"><font color="blue" size="3"><u>linux-2.6.35.9.tar.bz</u></font></a><font size="3"> <br> <br> Then run: <br> ~$ cd ~/next3-utils/patch <br> ~/next3-utils/patch$ make next3_snapshot <br> <br> This may take some time to unpack files from kernel tar ball and should eventually create the patch file next3_snapshot.module.patch <br> and copy it to the ~/kernel/2.6.35/ dir. <br> <br> This is the same patch that is being downloaded from the web site for all supported kernels (2.6.31-35). <br> If you copy it to ~/next3-util and run 'make module' in that directory, it should build the latest next3 version <br> for your kernel (2.6.32), which you can test by running 'sudo make test'. <br> <br> I am pretty sure I missed something in the instructions, so please let me know how far you got <br> and we'll take it from there. <br> <br> Thanks, <br> Amir. <br> <br> <br> On Fri, Apr 27, 2012 at 3:07 PM, Kim Hagen <</font><a href="mailto:kh...@mu..." target="_blank"><font color="blue" size="3"><u>kh...@mu...</u></font></a><font size="3">> wrote: </font><font face="sans-serif" size="3"><br> Hi Amir,</font><font size="3"> </font><font face="sans-serif" size="3"><br> <br> 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?)</font><font size="3"> </font><font face="sans-serif" size="3"><br> <br> Kind regards,</font><font size="3"> </font><font face="sans-serif" size="3"><br> <br> Kim</font><font size="3"> <br> <br> <br> <br> <br> </font><font face="sans-serif" size="3"><br> <br> <br> This message contains information that may be priviliged or confidential and is intended only for use by the addressee(s).<br> You are not authorized to use or distribute this message or any part of it in any form, unless you are the intended recipient.<br> 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.<br> <br> 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: </font><a href="mailto:no...@mu..." target="_blank"><font color="blue" face="sans-serif" size="3"><u>no...@mu...</u></font></a><font face="sans-serif" size="3"><br> Multi Corporation B.V., Gouda, is registered with the trade register in the Netherlands under no. 34237857.<br> <br> -------------------------------------------------------------------------------------------------------------------------------<br> <br> Dit bericht bevat informatie die vertrouwelijk kan zijn en is uitsluitend bestemd voor de geadresseerde(n).<br> 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.<br> 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. <br> <br> Indien u geen email meer wilt ontvangen van Multi Corporation of haar groepsvennootschappen kunt u dit kenbaar maken door een email te sturen naar : </font><a href="mailto:no...@mu..." target="_blank"><font color="blue" face="sans-serif" size="3"><u>no...@mu...</u></font></a><font face="sans-serif" size="3"><br> Multi Corporation B.V., Gouda, staat ingeschreven in de Kamer van Koophandel onder nr. 34237857.</font><font size="3"> <br> <br> <br> </font><font face="sans-serif"><br> <br> <br> <br> This message contains information that may be priviliged or confidential and is intended only for use by the addressee(s).<br> You are not authorized to use or distribute this message or any part of it in any form, unless you are the intended recipient.<br> 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.<br> <br> 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: </font><a href="mailto:no...@mu..." target="_blank"><font color="blue" face="sans-serif"><u>no...@mu...</u></font></a><font face="sans-serif"><br> Multi Corporation B.V., Gouda, is registered with the trade register in the Netherlands under no. 34237857.<br> <br> -------------------------------------------------------------------------------------------------------------------------------<br> <br> Dit bericht bevat informatie die vertrouwelijk kan zijn en is uitsluitend bestemd voor de geadresseerde(n).<br> 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.<br> 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. <br> <br> Indien u geen email meer wilt ontvangen van Multi Corporation of haar groepsvennootschappen kunt u dit kenbaar maken door een email te sturen naar : </font><a href="mailto:no...@mu..." target="_blank"><font color="blue" face="sans-serif"><u>no...@mu...</u></font></a><font face="sans-serif"><br> Multi Corporation B.V., Gouda, staat ingeschreven in de Kamer van Koophandel onder nr. 34237857.</font><font size="3"> <br> <br> <br> <br> </font></div></div><font face="sans-serif"><div><div class="h5"><br> <br> <br> This message contains information that may be priviliged or confidential and is intended only for use by the addressee(s).<br> You are not authorized to use or distribute this message or any part of it in any form, unless you are the intended recipient.<br> 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.<br> <br> 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: <a href="mailto:no...@mu..." target="_blank">no...@mu...</a><br> Multi Corporation B.V., Gouda, is registered with the trade register in the Netherlands under no. 34237857.<br> <br> -------------------------------------------------------------------------------------------------------------------------------<br> <br> Dit bericht bevat informatie die vertrouwelijk kan zijn en is uitsluitend bestemd voor de geadresseerde(n).<br> 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.<br> 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. <br> <br> Indien u geen email meer wilt ontvangen van Multi Corporation of haar groepsvennootschappen kunt u dit kenbaar maken door een email te sturen naar : <a href="mailto:no...@mu..." target="_blank">no...@mu...</a><br></div></div><div class="im"> Multi Corporation B.V., Gouda, staat ingeschreven in de Kamer van Koophandel onder nr. 34237857.</div></font><font size="3"> </font><tt><font face="Courier New,Courier,monospace" size="2">------------------------------------------------------------------------------<div class="im"><br> Live Security Virtual Conference<br> Exclusive live event will cover all the ways today's security and <br> threat landscape has changed and how IT managers can respond. Discussions <br> will include endpoint security, mobile security and the latest in malware <br> threats. </div></font></tt><a href="http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/" target="_blank"><tt><font face="Courier New,Courier,monospace" size="2">http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/</font></tt></a><tt><font face="Courier New,Courier,monospace" size="2">_______________________________________________<br> Next3-users mailing list<br> <a href="mailto:Nex...@li..." target="_blank">Nex...@li...</a><br> </font></tt><a href="https://lists.sourceforge.net/lists/listinfo/next3-users" target="_blank"><tt><font face="Courier New,Courier,monospace" size="2">https://lists.sourceforge.net/lists/listinfo/next3-users</font></tt></a><tt><font face="Courier New,Courier,monospace" size="2"><br> </font></tt> <br> <br> <br> <br> <span style="font-size:10pt;font-family:sans-serif,helvetica"><br><div class="im"> <br> This message contains information that may be priviliged or confidential and is intended only for use by the addressee(s).<br> You are not authorized to use or distribute this message or any part of it in any form, unless you are the intended recipient.<br> 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.<br> <br> 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: <a href="mailto:no...@mu..." target="_blank">no...@mu...</a><br> Multi Corporation B.V., Gouda, is registered with the trade register in the Netherlands under no. 34237857.<br> <br> -------------------------------------------------------------------------------------------------------------------------------<br> <br> Dit bericht bevat informatie die vertrouwelijk kan zijn en is uitsluitend bestemd voor de geadresseerde(n).<br> 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.<br> 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. <br> <br> Indien u geen email meer wilt ontvangen van Multi Corporation of haar groepsvennootschappen kunt u dit kenbaar maken door een email te sturen naar : <a href="mailto:no...@mu..." target="_blank">no...@mu...</a><br> Multi Corporation B.V., Gouda, staat ingeschreven in de Kamer van Koophandel onder nr. 34237857.</div></span> </blockquote></div><br></div></div> </div></div></font><br> <br> <br> <span style="font-family:sans-serif,helvetica; font-size:10pt; color:#000000"><br> <br> This message contains information that may be priviliged or confidential and is intended only for use by the addressee(s).<br> You are not authorized to use or distribute this message or any part of it in any form, unless you are the intended recipient.<br> 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.<br> <br> 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...<br> Multi Corporation B.V., Gouda, is registered with the trade register in the Netherlands under no. 34237857.<br> <br> -------------------------------------------------------------------------------------------------------------------------------<br> <br> Dit bericht bevat informatie die vertrouwelijk kan zijn en is uitsluitend bestemd voor de geadresseerde(n).<br> 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.<br> 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. <br> <br> 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...<br> Multi Corporation B.V., Gouda, staat ingeschreven in de Kamer van Koophandel onder nr. 34237857.</span> |
