next3-users Mailing List for NEXT3
Brought to you by:
amir73il
Menu
▾
▴
next3-users — Next3 users news and support
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
(4) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(14) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(8) |
May
(11) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(7) |
Nov
|
Dec
|
| 2013 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Manik M. <man...@su...> - 2013-01-27 06:52:45
|
Hi All, Actully i need to know about attribute details of next3 snapshot. And how suppose to be delete that snapshot and what is going at background......... Need deep knowledge about this.......................... -- Regards, Manik Mhangare. -- Confidentiality Note: This e-mail message and any attachments to it are intended only for the named recipients and may contain legally privileged and/or confidential information. If you are not one of the intended recipients, please forward this mail to ab...@su... and do not duplicate or forward this e-mail message and immediately delete it from your computer. |
|
From: Amir G. <ami...@gm...> - 2012-10-24 18:35:47
|
Glad to hear. SF.net projects web servers were upgraded this week. I also had to fix the cgi-bin scripts, who were out of date, so now all seems to be up and running again. Thanks for reporting the problem. Amir. On Tue, Oct 23, 2012 at 11:11 PM, James Sefton <ja...@ph...> wrote: > Worked nicely. J**** > > ** ** > > *From:* James Sefton [mailto:ja...@ph...] > *Sent:* 23 October 2012 22:00 > *To:* Amir Goldstein > > *Cc:* nex...@li... > *Subject:* Re: [Next3-users] Cannot install?**** > > ** ** > > Many thanks Amir,**** > > ** ** > > I will give it another try now.**** > > ** ** > > My next3_fs patch is for 2.6.35 – I happened to download it when messing > around before. > I have brought the kernel up to that version now. I was trying 2.6.32 > because I could not get others to work. (Thinking the version was not > supported at the time)**** > > ** ** > > Thanks again for your help.**** > > I am sure once next3.sf.net is fixed, all will work as flawlessly as it > always has.**** > > ** ** > > Regards,**** > > ** ** > > James**** > > ** ** > > *From:* Amir Goldstein [mailto:ami...@gm... <ami...@gm...>] > *Sent:* 23 October 2012 21:56 > *To:* James Sefton > *Cc:* nex...@li... > *Subject:* Re: [Next3-users] Cannot install?**** > > ** ** > > ** ** > > On Tue, Oct 23, 2012 at 10:09 PM, James Sefton <ja...@ph...> wrote: > **** > > That doesn’t work in my browser or with wget.**** > > It just says ‘connection was reset’.**** > > **** > > I cannot even view next3.sourceforge.net or next3.sf.net in my browser.*** > * > > **** > > I guess sourceforge is broken.**** > > ** ** > > I guess so..**** > > **** > > **** > > I have a copy of next3_fs.module.patch **** > > ** ** > > is this the patch for your kernel (2.6.32)?**** > > ** ** > > but I am still missing next3_snapshot.module.patch. **** > > Is there by any chance a copy of the files hosted anywhere else?**** > > ** ** > > hosted on my PC ;-)**** > > see attached latest version from Aug 2, 2011.**** > > good for kernels 2.6.32-2.6.35.**** > > **** > > **** > > If not then I guess I will just need to wait until sourceforge gets fixed. > **** > > **** > > Cheers,**** > > **** > > James**** > > **** > > *From:* Amir Goldstein [mailto:ami...@gm...] > *Sent:* 23 October 2012 04:58 > *To:* James Sefton > *Cc:* nex...@li... > *Subject:* Re: [Next3-users] Cannot install?**** > > **** > > Sent from my private persona, enabled by Cellrox > On Oct 23, 2012 4:18 AM, "James Sefton" <ja...@ph...> wrote: > > > > Hi, > > > > > > > > I have used Next3 for quite some time. > > > > I just came to set-up an additional server and find that it is unable to > download the patch for the kernel. > > > > I tried various kernel versions within what is listed as supported in > the changelog but it always says not found. > > > > > > > > Have the patches been removed? > >**** > > No, but maybe sf.net cgi scripts are not working. Ill check.**** > > You can download the patch before make from: > > http://next3.sourceforge.net/files/1.0.13/linux-2.6.32/next3_fs.module.patch > **** > > Then make will not try to download it.**** > > Cheers, > Amir.**** > > > > > > > Cheers, > > > > > > > > James > > > > > > > > > > > > Here is just one example of what happens: > > > > > > > > root@ubuntu:~/next3-1.0.13# <root@ubuntu:~/next3-1.0.13> make > > > > downloading next3 patches for kernel 2.6.32-44-server... > > > > # some wget support --trust-server-names, others don't > > > > --2012-10-23 02:43:51-- > http://next3.sf.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > > > Resolving next3.sf.net... 216.34.181.96 > > > > Connecting to next3.sf.net|216.34.181.96|:80... connected. > > > > HTTP request sent, awaiting response... 302 Found > > > > Location: > http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64[following] > > > > --2012-10-23 02:43:51-- > http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > > > Resolving next3.sourceforge.net... 216.34.181.96 > > > > Reusing existing connection to next3.sf.net:80. > > > > HTTP request sent, awaiting response... 404 Not Found > > > > 2012-10-23 02:43:51 ERROR 404: Not Found. > > > > > > > > --2012-10-23 02:43:51-- > http://next3.sf.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > > > Resolving next3.sf.net... 216.34.181.96 > > > > Connecting to next3.sf.net|216.34.181.96|:80... connected. > > > > HTTP request sent, awaiting response... 302 Found > > > > Location: > http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64[following] > > > > --2012-10-23 02:43:52-- > http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > > > Resolving next3.sourceforge.net... 216.34.181.96 > > > > Reusing existing connection to next3.sf.net:80. > > > > HTTP request sent, awaiting response... 404 Not Found > > > > 2012-10-23 02:43:52 ERROR 404: Not Found. > > > > > > > > Sorry, next3_fs.module.patch is not available for kernel > 2.6.32-44-server. Please check http://next3.sf.net for new releases. > > > > make: *** [next3_fs.module.patch] Error 1 > > > > > > > ------------------------------------------------------------------------------ > > Everyone hates slow websites. So do we. > > Make your web apps faster with AppDynamics > > Download AppDynamics Lite for free today: > > http://p.sf.net/sfu/appdyn_sfd2d_oct > > _______________________________________________ > > Next3-users mailing list > > Nex...@li... > > https://lists.sourceforge.net/lists/listinfo/next3-users > >**** > > ** ** > |
|
From: James S. <ja...@ph...> - 2012-10-23 21:31:19
|
Worked nicely. :) From: James Sefton [mailto:ja...@ph...] Sent: 23 October 2012 22:00 To: Amir Goldstein Cc: nex...@li... Subject: Re: [Next3-users] Cannot install? Many thanks Amir, I will give it another try now. My next3_fs patch is for 2.6.35 - I happened to download it when messing around before. I have brought the kernel up to that version now. I was trying 2.6.32 because I could not get others to work. (Thinking the version was not supported at the time) Thanks again for your help. I am sure once next3.sf.net is fixed, all will work as flawlessly as it always has. Regards, James From: Amir Goldstein [mailto:ami...@gm...] Sent: 23 October 2012 21:56 To: James Sefton Cc: nex...@li...<mailto:nex...@li...> Subject: Re: [Next3-users] Cannot install? On Tue, Oct 23, 2012 at 10:09 PM, James Sefton <ja...@ph...<mailto:ja...@ph...>> wrote: That doesn't work in my browser or with wget. It just says 'connection was reset'. I cannot even view next3.sourceforge.net<http://next3.sourceforge.net> or next3.sf.net<http://next3.sf.net> in my browser. I guess sourceforge is broken. I guess so.. I have a copy of next3_fs.module.patch is this the patch for your kernel (2.6.32)? but I am still missing next3_snapshot.module.patch. Is there by any chance a copy of the files hosted anywhere else? hosted on my PC ;-) see attached latest version from Aug 2, 2011. good for kernels 2.6.32-2.6.35. If not then I guess I will just need to wait until sourceforge gets fixed. Cheers, James From: Amir Goldstein [mailto:ami...@gm...<mailto:ami...@gm...>] Sent: 23 October 2012 04:58 To: James Sefton Cc: nex...@li...<mailto:nex...@li...> Subject: Re: [Next3-users] Cannot install? Sent from my private persona, enabled by Cellrox On Oct 23, 2012 4:18 AM, "James Sefton" <ja...@ph...<mailto:ja...@ph...>> wrote: > > Hi, > > > > I have used Next3 for quite some time. > > I just came to set-up an additional server and find that it is unable to download the patch for the kernel. > > I tried various kernel versions within what is listed as supported in the changelog but it always says not found. > > > > Have the patches been removed? > No, but maybe sf.net<http://sf.net> cgi scripts are not working. Ill check. You can download the patch before make from: http://next3.sourceforge.net/files/1.0.13/linux-2.6.32/next3_fs.module.patch Then make will not try to download it. Cheers, Amir. > > > Cheers, > > > > James > > > > > > Here is just one example of what happens: > > > > root@ubuntu:~/next3-1.0.13#<mailto:root@ubuntu:~/next3-1.0.13> make > > downloading next3 patches for kernel 2.6.32-44-server... > > # some wget support --trust-server-names, others don't > > --2012-10-23 02:43:51-- http://next3.sf.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > Resolving next3.sf.net... 216.34.181.96<tel:216.34.181.96> > > Connecting to next3.sf.net<http://next3.sf.net>|216.34.181.96<tel:216.34.181.96>|:80... connected. > > HTTP request sent, awaiting response... 302 Found > > Location: http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 [following] > > --2012-10-23 02:43:51-- http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > Resolving next3.sourceforge.net... 216.34.181.96<tel:216.34.181.96> > > Reusing existing connection to next3.sf.net:80<http://next3.sf.net:80>. > > HTTP request sent, awaiting response... 404 Not Found > > 2012-10-23 02:43:51 ERROR 404: Not Found. > > > > --2012-10-23 02:43:51-- http://next3.sf.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > Resolving next3.sf.net... 216.34.181.96<tel:216.34.181.96> > > Connecting to next3.sf.net<http://next3.sf.net>|216.34.181.96<tel:216.34.181.96>|:80... connected. > > HTTP request sent, awaiting response... 302 Found > > Location: http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 [following] > > --2012-10-23 02:43:52-- http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > Resolving next3.sourceforge.net... 216.34.181.96<tel:216.34.181.96> > > Reusing existing connection to next3.sf.net:80<http://next3.sf.net:80>. > > HTTP request sent, awaiting response... 404 Not Found > > 2012-10-23 02:43:52 ERROR 404: Not Found. > > > > Sorry, next3_fs.module.patch is not available for kernel 2.6.32-44-server. Please check http://next3.sf.net for new releases. > > make: *** [next3_fs.module.patch] Error 1 > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > Next3-users mailing list > Nex...@li...<mailto:Nex...@li...> > https://lists.sourceforge.net/lists/listinfo/next3-users > |
|
From: James S. <ja...@ph...> - 2012-10-23 21:00:31
|
Many thanks Amir, I will give it another try now. My next3_fs patch is for 2.6.35 - I happened to download it when messing around before. I have brought the kernel up to that version now. I was trying 2.6.32 because I could not get others to work. (Thinking the version was not supported at the time) Thanks again for your help. I am sure once next3.sf.net is fixed, all will work as flawlessly as it always has. Regards, James From: Amir Goldstein [mailto:ami...@gm...] Sent: 23 October 2012 21:56 To: James Sefton Cc: nex...@li... Subject: Re: [Next3-users] Cannot install? On Tue, Oct 23, 2012 at 10:09 PM, James Sefton <ja...@ph...<mailto:ja...@ph...>> wrote: That doesn't work in my browser or with wget. It just says 'connection was reset'. I cannot even view next3.sourceforge.net<http://next3.sourceforge.net> or next3.sf.net<http://next3.sf.net> in my browser. I guess sourceforge is broken. I guess so.. I have a copy of next3_fs.module.patch is this the patch for your kernel (2.6.32)? but I am still missing next3_snapshot.module.patch. Is there by any chance a copy of the files hosted anywhere else? hosted on my PC ;-) see attached latest version from Aug 2, 2011. good for kernels 2.6.32-2.6.35. If not then I guess I will just need to wait until sourceforge gets fixed. Cheers, James From: Amir Goldstein [mailto:ami...@gm...<mailto:ami...@gm...>] Sent: 23 October 2012 04:58 To: James Sefton Cc: nex...@li...<mailto:nex...@li...> Subject: Re: [Next3-users] Cannot install? Sent from my private persona, enabled by Cellrox On Oct 23, 2012 4:18 AM, "James Sefton" <ja...@ph...<mailto:ja...@ph...>> wrote: > > Hi, > > > > I have used Next3 for quite some time. > > I just came to set-up an additional server and find that it is unable to download the patch for the kernel. > > I tried various kernel versions within what is listed as supported in the changelog but it always says not found. > > > > Have the patches been removed? > No, but maybe sf.net<http://sf.net> cgi scripts are not working. Ill check. You can download the patch before make from: http://next3.sourceforge.net/files/1.0.13/linux-2.6.32/next3_fs.module.patch Then make will not try to download it. Cheers, Amir. > > > Cheers, > > > > James > > > > > > Here is just one example of what happens: > > > > root@ubuntu:~/next3-1.0.13#<mailto:root@ubuntu:~/next3-1.0.13> make > > downloading next3 patches for kernel 2.6.32-44-server... > > # some wget support --trust-server-names, others don't > > --2012-10-23 02:43:51-- http://next3.sf.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > Resolving next3.sf.net... 216.34.181.96<tel:216.34.181.96> > > Connecting to next3.sf.net<http://next3.sf.net>|216.34.181.96<tel:216.34.181.96>|:80... connected. > > HTTP request sent, awaiting response... 302 Found > > Location: http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 [following] > > --2012-10-23 02:43:51-- http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > Resolving next3.sourceforge.net... 216.34.181.96<tel:216.34.181.96> > > Reusing existing connection to next3.sf.net:80<http://next3.sf.net:80>. > > HTTP request sent, awaiting response... 404 Not Found > > 2012-10-23 02:43:51 ERROR 404: Not Found. > > > > --2012-10-23 02:43:51-- http://next3.sf.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > Resolving next3.sf.net... 216.34.181.96<tel:216.34.181.96> > > Connecting to next3.sf.net<http://next3.sf.net>|216.34.181.96<tel:216.34.181.96>|:80... connected. > > HTTP request sent, awaiting response... 302 Found > > Location: http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 [following] > > --2012-10-23 02:43:52-- http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > Resolving next3.sourceforge.net... 216.34.181.96<tel:216.34.181.96> > > Reusing existing connection to next3.sf.net:80<http://next3.sf.net:80>. > > HTTP request sent, awaiting response... 404 Not Found > > 2012-10-23 02:43:52 ERROR 404: Not Found. > > > > Sorry, next3_fs.module.patch is not available for kernel 2.6.32-44-server. Please check http://next3.sf.net for new releases. > > make: *** [next3_fs.module.patch] Error 1 > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > Next3-users mailing list > Nex...@li...<mailto:Nex...@li...> > https://lists.sourceforge.net/lists/listinfo/next3-users > |
|
From: James S. <ja...@ph...> - 2012-10-23 20:30:08
|
That doesn't work in my browser or with wget. It just says 'connection was reset'. I cannot even view next3.sourceforge.net or next3.sf.net in my browser. I guess sourceforge is broken. I have a copy of next3_fs.module.patch but I am still missing next3_snapshot.module.patch. Is there by any chance a copy of the files hosted anywhere else? If not then I guess I will just need to wait until sourceforge gets fixed. Cheers, James From: Amir Goldstein [mailto:ami...@gm...] Sent: 23 October 2012 04:58 To: James Sefton Cc: nex...@li... Subject: Re: [Next3-users] Cannot install? Sent from my private persona, enabled by Cellrox On Oct 23, 2012 4:18 AM, "James Sefton" <ja...@ph...<mailto:ja...@ph...>> wrote: > > Hi, > > > > I have used Next3 for quite some time. > > I just came to set-up an additional server and find that it is unable to download the patch for the kernel. > > I tried various kernel versions within what is listed as supported in the changelog but it always says not found. > > > > Have the patches been removed? > No, but maybe sf.net<http://sf.net> cgi scripts are not working. Ill check. You can download the patch before make from: http://next3.sourceforge.net/files/1.0.13/linux-2.6.32/next3_fs.module.patch Then make will not try to download it. Cheers, Amir. > > > Cheers, > > > > James > > > > > > Here is just one example of what happens: > > > > root@ubuntu:~/next3-1.0.13#<mailto:root@ubuntu:~/next3-1.0.13#> make > > downloading next3 patches for kernel 2.6.32-44-server... > > # some wget support --trust-server-names, others don't > > --2012-10-23 02:43:51-- http://next3.sf.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > Resolving next3.sf.net... 216.34.181.96 > > Connecting to next3.sf.net<http://next3.sf.net>|216.34.181.96|:80... connected. > > HTTP request sent, awaiting response... 302 Found > > Location: http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 [following] > > --2012-10-23 02:43:51-- http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > Resolving next3.sourceforge.net... 216.34.181.96 > > Reusing existing connection to next3.sf.net:80<http://next3.sf.net:80>. > > HTTP request sent, awaiting response... 404 Not Found > > 2012-10-23 02:43:51 ERROR 404: Not Found. > > > > --2012-10-23 02:43:51-- http://next3.sf.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > Resolving next3.sf.net... 216.34.181.96 > > Connecting to next3.sf.net<http://next3.sf.net>|216.34.181.96|:80... connected. > > HTTP request sent, awaiting response... 302 Found > > Location: http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 [following] > > --2012-10-23 02:43:52-- http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > Resolving next3.sourceforge.net... 216.34.181.96 > > Reusing existing connection to next3.sf.net:80<http://next3.sf.net:80>. > > HTTP request sent, awaiting response... 404 Not Found > > 2012-10-23 02:43:52 ERROR 404: Not Found. > > > > Sorry, next3_fs.module.patch is not available for kernel 2.6.32-44-server. Please check http://next3.sf.net for new releases. > > make: *** [next3_fs.module.patch] Error 1 > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > Next3-users mailing list > Nex...@li...<mailto:Nex...@li...> > https://lists.sourceforge.net/lists/listinfo/next3-users > |
|
From: Amir G. <ami...@gm...> - 2012-10-23 03:58:33
|
Sent from my private persona, enabled by Cellrox On Oct 23, 2012 4:18 AM, "James Sefton" <ja...@ph...> wrote: > > Hi, > > > > I have used Next3 for quite some time. > > I just came to set-up an additional server and find that it is unable to download the patch for the kernel. > > I tried various kernel versions within what is listed as supported in the changelog but it always says not found. > > > > Have the patches been removed? > No, but maybe sf.net cgi scripts are not working. Ill check. You can download the patch before make from: http://next3.sourceforge.net/files/1.0.13/linux-2.6.32/next3_fs.module.patch Then make will not try to download it. Cheers, Amir. > > > Cheers, > > > > James > > > > > > Here is just one example of what happens: > > > > root@ubuntu:~/next3-1.0.13# make > > downloading next3 patches for kernel 2.6.32-44-server... > > # some wget support --trust-server-names, others don't > > --2012-10-23 02:43:51-- http://next3.sf.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > Resolving next3.sf.net... 216.34.181.96 > > Connecting to next3.sf.net|216.34.181.96|:80... connected. > > HTTP request sent, awaiting response... 302 Found > > Location: http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64[following] > > --2012-10-23 02:43:51-- http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > Resolving next3.sourceforge.net... 216.34.181.96 > > Reusing existing connection to next3.sf.net:80. > > HTTP request sent, awaiting response... 404 Not Found > > 2012-10-23 02:43:51 ERROR 404: Not Found. > > > > --2012-10-23 02:43:51-- http://next3.sf.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > Resolving next3.sf.net... 216.34.181.96 > > Connecting to next3.sf.net|216.34.181.96|:80... connected. > > HTTP request sent, awaiting response... 302 Found > > Location: http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64[following] > > --2012-10-23 02:43:52-- http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 > > Resolving next3.sourceforge.net... 216.34.181.96 > > Reusing existing connection to next3.sf.net:80. > > HTTP request sent, awaiting response... 404 Not Found > > 2012-10-23 02:43:52 ERROR 404: Not Found. > > > > Sorry, next3_fs.module.patch is not available for kernel 2.6.32-44-server. Please check http://next3.sf.net for new releases. > > make: *** [next3_fs.module.patch] Error 1 > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > Next3-users mailing list > Nex...@li... > https://lists.sourceforge.net/lists/listinfo/next3-users > |
|
From: James S. <ja...@ph...> - 2012-10-23 02:18:42
|
Hi, I have used Next3 for quite some time. I just came to set-up an additional server and find that it is unable to download the patch for the kernel. I tried various kernel versions within what is listed as supported in the changelog but it always says not found. Have the patches been removed? Cheers, James Here is just one example of what happens: root@ubuntu:~/next3-1.0.13# make downloading next3 patches for kernel 2.6.32-44-server... # some wget support --trust-server-names, others don't --2012-10-23 02:43:51-- http://next3.sf.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 Resolving next3.sf.net... 216.34.181.96 Connecting to next3.sf.net|216.34.181.96|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 [following] --2012-10-23 02:43:51-- http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 Resolving next3.sourceforge.net... 216.34.181.96 Reusing existing connection to next3.sf.net:80. HTTP request sent, awaiting response... 404 Not Found 2012-10-23 02:43:51 ERROR 404: Not Found. --2012-10-23 02:43:51-- http://next3.sf.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 Resolving next3.sf.net... 216.34.181.96 Connecting to next3.sf.net|216.34.181.96|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 [following] --2012-10-23 02:43:52-- http://next3.sourceforge.net/cgi-bin/download?f=next3_fs.module.patch&v=1.0.13&r=2.6.32-44-server&m=x86_64 Resolving next3.sourceforge.net... 216.34.181.96 Reusing existing connection to next3.sf.net:80. HTTP request sent, awaiting response... 404 Not Found 2012-10-23 02:43:52 ERROR 404: Not Found. Sorry, next3_fs.module.patch is not available for kernel 2.6.32-44-server. Please check http://next3.sf.net for new releases. make: *** [next3_fs.module.patch] Error 1 |
|
From: Amir G. <ami...@us...> - 2012-08-09 18:09:20
|
Hi, Can you please specify your kernel version (uname -a) and next3 version (./bin/next3 version) Also, were any errors reported from the kernel module? please attach an output of dmesg after the test fails. Thanks, Amir. On Thu, Aug 9, 2012 at 1:14 PM, <nex...@li...>wrote: > > > > ---------- Forwarded message ---------- > From: spdave spdave <so...@gm...> > To: nex...@li... > Cc: > Date: Thu, 9 Aug 2012 16:44:08 +0530 > Subject: mkdir: cannot create directory `/next3-1.0.13/test/A': Permission > denied > I get the "Permission denied" error when i run "make test"(used to test > snapshot functionality). It fails to create file/folder in test directory. > > > *************************************************************************************************************************************************************** > [root@localhost next3-1.0.13]# sudo make test > grep next3 /proc/modules || /sbin/insmod next3/next3.ko > next3 203349 0 - Live 0xffffffffa03f7000 > jbd 50743 1 next3, Live 0xffffffffa03e8000 > mbcache 7462 2 next3,ext4, Live 0xffffffffa00b4000 > (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 ) > mke2fs 1.41.14-next3-1.0.13-1 (22-Feb-2011) > test.img is not a block special device. > Proceed anyway? (y,n) Filesystem label= > OS type: Linux > Block size=4096 (log=2) > Fragment size=4096 (log=2) > Stride=0 blocks, Stripe width=0 blocks > 262144 inodes, 1048576 blocks > 52428 blocks (5.00%) reserved for the super user > First data block=0 > Maximum filesystem blocks=1073741824 > 32 block groups > 32768 blocks per group, 32768 fragments per group > 8192 inodes per group > Superblock backups stored on blocks: > 32768, 98304, 163840, 229376, 294912, 819200, 884736 > > Writing inode tables: done > > Filesystem too small for requested journal size. Creating a smaller > journal. > Creating journal (32768 blocks): done > Writing superblocks and filesystem accounting information: done > > This filesystem will be automatically checked every 35 mounts or > 180 days, whichever comes first. Use tune2fs -c or -i to override. > tune2fs 1.41.14-next3-1.0.13-1 (22-Feb-2011) > Setting error behavior to 2 > next3 filesystem created on test.img > . > mkdir -p test > chmod -R 777 test > mount -t next3 | grep test || mount -t next3 test.img -o loop test > ./bin/next3 tests > mkdir: cannot create directory `/next3-1.0.13/test/A': Permission denied > mkdir: cannot create directory `/next3-1.0.13/test/B': Permission denied > mkdir: cannot create directory `/next3-1.0.13/test/C': Permission denied > mkdir: cannot create directory `/next3-1.0.13/test/D': Permission denied > mkdir: cannot create directory `/next3-1.0.13/test/E': Permission denied > ./bin/next3: line 525: /next3-1.0.13/test/A/a.txt: No such file or > directory > ./bin/next3: line 526: /next3-1.0.13/test/B/b.txt: No such file or > directory > ./bin/next3: line 527: /next3-1.0.13/test/C/c.txt: No such file or > directory > mkdir: cannot create directory `/next3-1.0.13/test/test': Permission denied > ./bin/chattr.next3: No such file or directory while trying to stat > /next3-1.0.13/test/test > > Running snapshot test 1: > ------------------------ > ./bin/next3: line 631: cd: /next3-1.0.13/test/test: No such file or > directory > Appending 1M zeros to 1M.1 with direct I/O > 1+0 records in > 1+0 records out > Writing 1M random data to 1 files > ./bin/next3: line 647: cd: OLDPWD not set > Files in file system: > grep: ?/*: No such file or directory > . > mkdir: cannot create directory `/next3-1.0.13/test/.snapshots': Permission > denied > make: *** [test] Error 1 > > *************************************************************************************************************************************************************** > > > Any idea's what might be the problem would be? > > Thanks in advance, > > > > |
|
From: 欧阳晓华 <toa...@gm...> - 2012-05-10 09:47:26
|
Thank you 2012/5/10 Amir Goldstein <ami...@gm...> > Hi, > > I do not support such old kernels, > but there is a port by OpenNode to RHEL 5, > which I have never tried myself. > > http://opennode.activesys.org/documentation/howtos/next3-snapshots/ > > Amir. > > On Thu, May 10, 2012 at 11:49 AM, 欧阳晓华 <toa...@gm...> wrote: > >> The kernel is 2.6.18-164 >> Can't find kernel patch on http://next3.sourceforge.net/files/1.0.13/ >> Thanks >> B.R >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Next3-users mailing list >> Nex...@li... >> https://lists.sourceforge.net/lists/listinfo/next3-users >> >> > |
|
From: Amir G. <ami...@gm...> - 2012-05-10 09:45:35
|
Hi, I do not support such old kernels, but there is a port by OpenNode to RHEL 5, which I have never tried myself. http://opennode.activesys.org/documentation/howtos/next3-snapshots/ Amir. On Thu, May 10, 2012 at 11:49 AM, 欧阳晓华 <toa...@gm...> wrote: > The kernel is 2.6.18-164 > Can't find kernel patch on http://next3.sourceforge.net/files/1.0.13/ > Thanks > B.R > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Next3-users mailing list > Nex...@li... > https://lists.sourceforge.net/lists/listinfo/next3-users > > |
|
From: 欧阳晓华 <toa...@gm...> - 2012-05-10 08:50:00
|
The kernel is 2.6.18-164 Can't find kernel patch on http://next3.sourceforge.net/files/1.0.13/ Thanks B.R |
|
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> |
|
From: Amir G. <ami...@gm...> - 2012-05-02 14:03:58
|
Kim, I am not sure why clone -b doesn't work, and there is no need to grant read access, but if you manage to clone the repo, just checkout the next3-stable branch: cd ~/next3-utils/linux-2.6.35.9 git checkout -b next3-stable origin/next3-stable Amir. On Wed, May 2, 2012 at 4:56 PM, Kim Hagen <kh...@mu...>wrote: > Amir, > > Can you grant me access to clone branch? > or am i doing something wrong. > > root@nl-gouda-07:~# git clone -b next3-stable git:// > github.com/amir73il/ext4-snapshots.git ~/next3-utils/linux-2.6.35.9 > 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 > > Kim > > > > From: Kim Hagen <kh...@mu...> > To: Amir Goldstein <ami...@gm...>, > Cc: nex...@li... > Date: 05/02/2012 03:03 PM > Subject: Re: [Next3-users] Kernel bug.. > ------------------------------ > > > > Hi Amir, > > Ok, the outcome: > /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)" > inside generated patch +#define > NEXT3_SNAPSHOT_VERSION "next3 snapshot v1.0.13-6 (2-May-2010)" > next3/snapshot.h #define > NEXT3_SNAPSHOT_VERSION "next3 snapshot v1.0.13-6 (2-May-2010)" > > In * > https://github.com/amir73il/ext4-snapshots/blob/ext4-snapshots/fs/next3/snapshot.h > *<https://github.com/amir73il/ext4-snapshots/blob/ext4-snapshots/fs/next3/snapshot.h> > the version is also "next3 snapshot v1.0.13-6 (2-May-2010)". > > I think i got the wrong branch with the git clone, i see the stable with > version "next3 snapshot v1.0.13-8 (2-Aug-2011)" I will try the correct > branch and let you know. > > Kind regards, > > Kim > > > > From: Amir Goldstein <ami...@gm...> > To: Kim Hagen <kh...@mu...>, > Cc: nex...@li... > Date: 05/02/2012 02:40 PM > Subject: Re: [Next3-users] Kernel bug.. > ------------------------------ > > > > 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...*<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...* <ami...@gm...>> > To: Kim Hagen <*kh...@mu...*<kh...@mu...>>, > > Cc: *nex...@li...*<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...*<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. > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. > http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Next3-users mailing list > Nex...@li... > https://lists.sourceforge.net/lists/listinfo/next3-users > > > > > > > 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. > |
|
From: Kim H. <kh...@mu...> - 2012-05-02 13:56:44
|
Amir, Can you grant me access to clone branch? or am i doing something wrong. root@nl-gouda-07:~# git clone -b next3-stable git://github.com/amir73il/ext4-snapshots.git ~/next3-utils/linux-2.6.35.9 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 Kim From: Kim Hagen <kh...@mu...> To: Amir Goldstein <ami...@gm...>, Cc: nex...@li... Date: 05/02/2012 03:03 PM Subject: Re: [Next3-users] Kernel bug.. Hi Amir, Ok, the outcome: /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)" inside generated patch +#define NEXT3_SNAPSHOT_VERSION "next3 snapshot v1.0.13-6 (2-May-2010)" next3/snapshot.h #define NEXT3_SNAPSHOT_VERSION "next3 snapshot v1.0.13-6 (2-May-2010)" In https://github.com/amir73il/ext4-snapshots/blob/ext4-snapshots/fs/next3/snapshot.h the version is also "next3 snapshot v1.0.13-6 (2-May-2010)". I think i got the wrong branch with the git clone, i see the stable with version "next3 snapshot v1.0.13-8 (2-Aug-2011)" I will try the correct branch and let you know. Kind regards, Kim From: Amir Goldstein <ami...@gm...> To: Kim Hagen <kh...@mu...>, Cc: nex...@li... Date: 05/02/2012 02:40 PM Subject: Re: [Next3-users] Kernel bug.. 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...> 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 -b next3-stable That went ok. 2. git clone git://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 -b next3-stable ~/next3-utils/linux-2.6.35.9" to " git clone https:// github.com/amir73il/ext4... etc" than it downloaded the git. 3. I downloaded the tar ball from 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] snapshot: snapshot (40) created Apr 28 00:13:29 nl-gouda-07 kernel: [14036.117712] snapshot: snapshot (40) activated Apr 28 00:13:29 nl-gouda-07 kernel: [14036.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] 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...> To: Kim Hagen <kh...@mu...>, Cc: 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 -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 -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 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...> 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... 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. 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. 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. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Next3-users mailing list Nex...@li... https://lists.sourceforge.net/lists/listinfo/next3-users 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. |
|
From: Kim H. <kh...@mu...> - 2012-05-02 13:03:31
|
Hi Amir, Ok, the outcome: /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)" inside generated patch +#define NEXT3_SNAPSHOT_VERSION "next3 snapshot v1.0.13-6 (2-May-2010)" next3/snapshot.h #define NEXT3_SNAPSHOT_VERSION "next3 snapshot v1.0.13-6 (2-May-2010)" In https://github.com/amir73il/ext4-snapshots/blob/ext4-snapshots/fs/next3/snapshot.h the version is also "next3 snapshot v1.0.13-6 (2-May-2010)". I think i got the wrong branch with the git clone, i see the stable with version "next3 snapshot v1.0.13-8 (2-Aug-2011)" I will try the correct branch and let you know. Kind regards, Kim From: Amir Goldstein <ami...@gm...> To: Kim Hagen <kh...@mu...>, Cc: nex...@li... Date: 05/02/2012 02:40 PM Subject: Re: [Next3-users] Kernel bug.. 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...> 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 -b next3-stable That went ok. 2. git clone git://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 -b next3-stable ~/next3-utils/linux-2.6.35.9" to " git clone https:// github.com/amir73il/ext4... etc" than it downloaded the git. 3. I downloaded the tar ball from 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] snapshot: snapshot (40) created Apr 28 00:13:29 nl-gouda-07 kernel: [14036.117712] snapshot: snapshot (40) activated Apr 28 00:13:29 nl-gouda-07 kernel: [14036.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] 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...> To: Kim Hagen <kh...@mu...>, Cc: 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 -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 -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 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...> 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... 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. 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. 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. |
|
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. > |
|
From: Kim H. <kh...@mu...> - 2012-05-02 11:56:33
|
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...> 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 -b next3-stable That went ok. 2. git clone git://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 -b next3-stable ~/next3-utils/linux-2.6.35.9" to " git clone https:// github.com/amir73il/ext4... etc" than it downloaded the git. 3. I downloaded the tar ball from 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] snapshot: snapshot (40) created Apr 28 00:13:29 nl-gouda-07 kernel: [14036.117712] snapshot: snapshot (40) activated Apr 28 00:13:29 nl-gouda-07 kernel: [14036.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] 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...> To: Kim Hagen <kh...@mu...>, Cc: 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 -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 -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 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...> 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... 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. 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. |
|
From: Amir G. <ami...@gm...> - 2012-05-02 11:27:56
|
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...>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 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] snapshot: snapshot > (40) created > Apr 28 00:13:29 nl-gouda-07 kernel: [14036.117712] snapshot: snapshot > (40) activated > Apr 28 00:13:29 nl-gouda-07 kernel: [14036.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] 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...> > To: Kim Hagen <kh...@mu...>, > Cc: 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... > 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. > |
|
From: Kim H. <kh...@mu...> - 2012-05-02 10:58:33
|
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 -b next3-stable That went ok. 2. git clone git://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 -b next3-stable ~/next3-utils/linux-2.6.35.9" to " git clone https:// github.com/amir73il/ext4... etc" than it downloaded the git. 3. I downloaded the tar ball from 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] snapshot: snapshot (40) created Apr 28 00:13:29 nl-gouda-07 kernel: [14036.117712] snapshot: snapshot (40) activated Apr 28 00:13:29 nl-gouda-07 kernel: [14036.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] 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...> To: Kim Hagen <kh...@mu...>, Cc: 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 -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 -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 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...> 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... 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. |
|
From: Amir G. <ami...@gm...> - 2012-04-27 18:34:17
|
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 -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 -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 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...>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 > > > |
|
From: Kim H. <kh...@mu...> - 2012-04-27 12:08:02
|
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 From: Amir Goldstein <ami...@gm...> To: Kim Hagen <kh...@mu...>, Cc: nex...@li... Date: 04/27/2012 01:25 PM Subject: Re: [Next3-users] Kernel bug.. Hi Kim, I see what the problem is. next3 version 1.0.13-6 had some bugs with regards to snapshot size > 4TB, which where resolved by this commit: https://github.com/amir73il/ext4-snapshots/commit/87a6639f2f440685d5a550b0ce759ad39e511e58 You need to upgrade to latest version 1.0.13-8 from Aug 2, 2011. Unfortunately, I seem to have neglected the next3 releases since I started releasing ext4-snapshots and this is the reason you did not get the latest next3 version when you installed it from the web site. I also did write any coherent documentation how to get the code from github and build the latests version. The Makefile used to create a release is in the next3-utils repository under patch directory: https://github.com/amir73il/next3-utils/blob/master/patch/Makefile If you like I can walk you through creating a new next3_snapshot.module.patch ('make next3_snapshot KERNEL=2.6.32') or you can wait until I clear some time to do it myself (and keep reminding me about it). Amir. On Fri, Apr 27, 2012 at 12:46 PM, Kim Hagen <kh...@mu...> wrote: Hi Amir, The crash happens every day we create a snapshot it has happened for 3 days straight. The size of our volume is 10TB. /dev/mapper/BackupData-BackupData 9.9T 478G 8.9T 5% --- Logical volume --- LV Name /dev/BackupData/BackupData VG Name BackupData LV UUID jndfk9-GYHb-6aqu-3MKV-fLml-OFd4-3qHJNg LV Write Access read/write LV Status available # open 1 LV Size 10.00 TiB Current LE 2621440 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 We have used this volume for 5 days, first 2 days were for testing (without rsync) we also installed next3 at the same time we started using the volume. The output of the fsck... (i had already removed the snapshot yesterday and removed the cron job that takes the snapshots): # fsck.next3 -nf -C0 /dev/mapper/BackupData-BackupData e2fsck 1.41.14-next3-1.0.13-1 (22-Feb-2011) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information BackupData: 519307/671088640 files (3.7% non-contiguous), 167287708/2684354560 blocks This is what is in the logs... (sorry for the length): Apr 26 07:00:02 nl-gouda-07 kernel: [71796.800005] snapshot: next3_snapshot_enable() called with snapshot file (ino=21061634) not on list Apr 26 07:00:02 nl-gouda-07 kernel: [71796.858621] snapshot: snapshot (36) created Apr 26 07:00:02 nl-gouda-07 kernel: [71797.094522] snapshot: snapshot (36) activated Apr 26 07:00:02 nl-gouda-07 kernel: [71797.096916] snapshot: snapshot (36) has been taken Apr 26 07:16:47 nl-gouda-07 kernel: [72802.630978] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:16:48 nl-gouda-07 kernel: [72803.712051] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:16:48 nl-gouda-07 kernel: [72803.773532] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:16:56 nl-gouda-07 kernel: [72810.923815] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:18:17 nl-gouda-07 kernel: [72892.729274] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:28:55 nl-gouda-07 kernel: [73530.588936] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:28:56 nl-gouda-07 kernel: [73530.839443] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:28:56 nl-gouda-07 kernel: [73531.517396] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:28:57 nl-gouda-07 kernel: [73532.444935] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:28:57 nl-gouda-07 kernel: [73532.491089] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:28:57 nl-gouda-07 kernel: [73532.758984] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:28:58 nl-gouda-07 kernel: [73533.479672] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:28:58 nl-gouda-07 kernel: [73533.747038] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:29:00 nl-gouda-07 kernel: [73535.182968] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:41:59 nl-gouda-07 kernel: [74314.708945] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:42:13 nl-gouda-07 kernel: [74328.253262] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:43:40 nl-gouda-07 kernel: [74415.359183] snapshot: next3_snapshot_get_undo_access(b:0/67162) failed! h_ref=1, err=-5 Apr 26 07:43:40 nl-gouda-07 kernel: [74415.359233] next3_try_to_allocate_with_rsv: aborting transaction: IO failure in __next3_journal_get_undo_access Apr 26 07:43:40 nl-gouda-07 kernel: [74415.359283] NEXT3-fs error (device dm-1) in next3_new_blocks: IO failure Apr 26 07:43:40 nl-gouda-07 kernel: [74415.361688] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem Apr 26 07:43:40 nl-gouda-07 kernel: [74415.363617] NEXT3-fs error (device dm-1) in next3_dirty_inode: IO failure Apr 26 07:43:40 nl-gouda-07 kernel: [74415.365512] NEXT3-fs error (device dm-1) in next3_inode_list_add: Readonly filesystem Apr 26 07:43:40 nl-gouda-07 kernel: [74415.367397] NEXT3-fs error (device dm-1) in next3_write_begin: IO failure Apr 26 07:43:40 nl-gouda-07 rsyncd[19142]: rsync: write failed on "/de-duisburg-02/file.pdf.restore" (in BackupData): Input/output error (5) Apr 26 07:43:40 nl-gouda-07 rsyncd[19142]: rsync error: error in file IO (code 11) at receiver.c(302) [receiver=3.0.7] Apr 26 07:43:40 nl-gouda-07 kernel: [74415.471732] snapshot: next3_snapshot_get_undo_access(b:0/67162) failed! h_ref=2, err=-5 Apr 26 07:43:40 nl-gouda-07 kernel: [74415.471781] __next3_free_blocks_sb_inode: aborting transaction: IO failure in __next3_journal_get_undo_access Apr 26 07:43:40 nl-gouda-07 kernel: [74415.471831] NEXT3-fs error (device dm-1) in __next3_free_blocks_sb_inode: IO failure Apr 26 07:43:40 nl-gouda-07 kernel: [74415.474006] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem Apr 26 07:43:40 nl-gouda-07 kernel: [74415.475918] NEXT3-fs error (device dm-1) in next3_truncate: IO failure Apr 26 07:43:40 nl-gouda-07 kernel: [74415.477827] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem Apr 26 07:43:40 nl-gouda-07 kernel: [74415.479708] NEXT3-fs error (device dm-1) in next3_inode_list_del: Readonly filesystem Apr 26 07:43:40 nl-gouda-07 kernel: [74415.481625] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem Apr 26 07:43:40 nl-gouda-07 kernel: [74415.483537] NEXT3-fs error (device dm-1) in next3_delete_inode: IO failure Apr 26 07:43:40 nl-gouda-07 rsyncd[19142]: rsync: connection unexpectedly closed (1491 bytes received so far) [generator] Apr 26 07:43:40 nl-gouda-07 rsyncd[19142]: rsync error: error in rsync protocol data stream (code 12) at io.c(601) [generator=3.0.7] Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638221] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638233] attempt to access beyond end of device Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638237] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638240] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638273] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638319] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638380] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:46:59 nl-gouda-07 kernel: [74614.640734] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:00 nl-gouda-07 kernel: [74615.254942] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:00 nl-gouda-07 kernel: [74615.254953] attempt to access beyond end of device Apr 26 07:47:00 nl-gouda-07 kernel: [74615.254956] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:00 nl-gouda-07 kernel: [74615.254963] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:00 nl-gouda-07 kernel: [74615.254995] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:00 nl-gouda-07 kernel: [74615.255041] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:00 nl-gouda-07 kernel: [74615.255089] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:00 nl-gouda-07 kernel: [74615.257408] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563027] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563037] attempt to access beyond end of device Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563041] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563044] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563077] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563123] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563171] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:00 nl-gouda-07 kernel: [74615.566488] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839271] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839285] attempt to access beyond end of device Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839288] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839293] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839326] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839372] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839421] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:01 nl-gouda-07 kernel: [74615.843553] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:03 nl-gouda-07 rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="1841" x-info="http://www.rsyslog.com"] rsyslogd was HUPed, type 'lightweight'. Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302879] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302888] attempt to access beyond end of device Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302892] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302896] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302928] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302975] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:05 nl-gouda-07 kernel: [74620.303023] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:05 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/......etc.Forum.pdf.fkslcK" (in BackupData) failed: Input/output error (5) Apr 26 07:47:05 nl-gouda-07 kernel: [74620.305387] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523632] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523641] attempt to access beyond end of device Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523645] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523649] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523681] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523727] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523776] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:05 nl-gouda-07 kernel: [74620.525947] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:05 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/....etc.pdf.9RoRu9" (in BackupData) failed: Input/output error (5) Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355528] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355537] attempt to access beyond end of device Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355541] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355545] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355577] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355632] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355681] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:06 nl-gouda-07 kernel: [74621.358001] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:06 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.fUXwdB" (in BackupData) failed: Input/output error (5) Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451537] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451545] attempt to access beyond end of device Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451548] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451552] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451583] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451630] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451678] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:06 nl-gouda-07 kernel: [74621.453915] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:06 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.pmPwd3" (in BackupData) failed: Input/output error (5) Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899588] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899598] attempt to access beyond end of device Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899601] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899605] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899637] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899683] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899731] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:07 nl-gouda-07 kernel: [74621.903637] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:07 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.zWyoww" (in BackupData) failed: Input/output error (5) Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571597] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571607] attempt to access beyond end of device Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571610] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571614] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571646] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571692] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571740] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:07 nl-gouda-07 kernel: [74622.574126] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:07 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.ZeByM1" (in BackupData) failed: Input/output error (5) Apr 26 07:47:07 nl-gouda-07 kernel: [74622.739001] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:07 nl-gouda-07 kernel: [74622.739009] attempt to access beyond end of device Apr 26 07:47:07 nl-gouda-07 kernel: [74622.739013] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:07 nl-gouda-07 kernel: [74622.739017] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:07 nl-gouda-07 kernel: [74622.745017] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:07 nl-gouda-07 kernel: [74622.745064] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:07 nl-gouda-07 kernel: [74622.745112] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:07 nl-gouda-07 kernel: [74622.747357] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:07 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.1uWVwx" (in BackupData) failed: Input/output error (5) Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289794] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289802] attempt to access beyond end of device Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289805] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289809] snapshot: failed to read COW bitmap #67169 of snapshot (36) Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289841] snapshot: next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289888] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289936] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:08 nl-gouda-07 kernel: [74623.292109] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:08 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.dwNJO4" (in BackupData) failed: Input/output error (5) Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547394] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547405] attempt to access beyond end of device Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547409] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547413] snapshot: failed to read COW bitmap #67169 of snapshot (36) Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547445] snapshot: next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547491] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547540] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:10 nl-gouda-07 kernel: [74625.550711] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:10 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.xjB0JI" (in BackupData) failed: Input/output error (5) Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131379] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131389] attempt to access beyond end of device Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131393] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131397] snapshot: failed to read COW bitmap #67169 of snapshot (36) Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131429] snapshot: next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131476] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131533] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:13 nl-gouda-07 kernel: [74628.134510] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:13 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.loyFbu" (in BackupData) failed: Input/output error (5) Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386694] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386703] attempt to access beyond end of device Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386707] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386711] snapshot: failed to read COW bitmap #67169 of snapshot (36) Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386743] snapshot: next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386789] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386837] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:15 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.L8Mocm" (in BackupData) failed: Input/output error (5) Apr 26 07:47:15 nl-gouda-07 kernel: [74630.389213] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584440] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584452] attempt to access beyond end of device Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584455] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584460] snapshot: failed to read COW bitmap #67169 of snapshot (36) Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584492] snapshot: next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584539] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584587] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:20 nl-gouda-07 kernel: [74635.587525] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:20 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.DjEhlt" (in BackupData) failed: Input/output error (5) Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203074] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203085] attempt to access beyond end of device Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203088] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203093] snapshot: failed to read COW bitmap #67169 of snapshot (36) Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203126] snapshot: next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203172] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203221] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:23 nl-gouda-07 kernel: [74638.207136] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:23 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.BdBO6H" (in BackupData) failed: Input/output error (5) Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278241] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278249] attempt to access beyond end of device Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278253] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278257] snapshot: failed to read COW bitmap #67171 of snapshot (36) Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278289] snapshot: next3_snapshot_get_write_access(b:1/67171) failed! h_ref=1, err=-5 Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278335] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278383] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:48:57 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.ls.Lj38Ce" (in BackupData) failed: Input/output error (5) Apr 26 07:48:57 nl-gouda-07 kernel: [74732.281008] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589644] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589654] attempt to access beyond end of device Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589657] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589661] snapshot: failed to read COW bitmap #67174 of snapshot (36) Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589694] snapshot: next3_snapshot_get_write_access(b:1/67174) failed! h_ref=1, err=-5 Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589740] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589788] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:50:10 nl-gouda-07 kernel: [74805.592176] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:50:10 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc (in BackupData) failed: Input/output error (5) Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603200] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603207] attempt to access beyond end of device Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603210] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603214] snapshot: failed to read COW bitmap #67174 of snapshot (36) Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603246] snapshot: next3_snapshot_get_write_access(b:1/67174) failed! h_ref=1, err=-5 Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603298] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603347] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:50:10 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.ls.NiNvWQ" (in BackupData) failed: Input/output error (5) Apr 26 07:50:10 nl-gouda-07 kernel: [74805.605316] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565081] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565091] attempt to access beyond end of device Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565094] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565098] snapshot: failed to read COW bitmap #67173 of snapshot (36) Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565131] snapshot: next3_snapshot_get_write_access(b:1/67173) failed! h_ref=1, err=-5 Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565177] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565225] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:50:43 nl-gouda-07 kernel: [74838.567610] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:50:43 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.9NvFJ9" (in BackupData) failed: Input/output error (5) Apr 26 07:50:44 nl-gouda-07 kernel: [74838.797944] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:50:44 nl-gouda-07 kernel: [74838.797952] attempt to access beyond end of device Apr 26 07:50:44 nl-gouda-07 kernel: [74838.797955] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:50:44 nl-gouda-07 kernel: [74838.797959] snapshot: failed to read COW bitmap #67173 of snapshot (36) Apr 26 07:50:44 nl-gouda-07 kernel: [74838.797991] snapshot: next3_snapshot_get_write_access(b:1/67173) failed! h_ref=1, err=-5 Apr 26 07:50:44 nl-gouda-07 kernel: [74838.798037] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:50:44 nl-gouda-07 kernel: [74838.798085] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:50:44 nl-gouda-07 kernel: [74838.800157] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:50:44 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc failed: Input/output error (5) Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802769] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802777] attempt to access beyond end of device Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802780] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802784] snapshot: failed to read COW bitmap #67173 of snapshot (36) Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802816] snapshot: next3_snapshot_get_write_access(b:1/67173) failed! h_ref=1, err=-5 Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802862] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802910] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:50:44 nl-gouda-07 kernel: [74838.805242] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:50:44 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.ppt.hcFvdt" (in BackupData) failed: Input/output error (5) Apr 26 08:01:42 nl-gouda-07 kernel: [75497.760927] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:06:20 nl-gouda-07 kernel: [75774.795683] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:08:33 nl-gouda-07 kernel: [75907.799568] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:08:58 nl-gouda-07 kernel: [75933.145117] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:05 nl-gouda-07 kernel: [75939.889330] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:12 nl-gouda-07 kernel: [75947.223080] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:25 nl-gouda-07 kernel: [75960.531557] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:43 nl-gouda-07 kernel: [75978.034688] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:50 nl-gouda-07 kernel: [75985.114594] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:50 nl-gouda-07 kernel: [75985.296441] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497242] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497254] ------------[ cut here ]------------ Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497275] WARNING: at /usr/src/next3-1.0.13/next3/snapshot.c:486 next3_snapshot_test_cow_bitmap+0x208/0x415 [next3]() Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497278] Hardware name: ProLiant DL380 G5 Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497279] Modules linked in: hcpdriver(P) cpufreq_conservative cpufreq_powersave cpufreq_userspace cpufreq_stats dm_round_robin dm_multipath scsi_dh loop radeon ttm drm_kms _helper drm i2c_algo_bit i2c_core i5000_edac snd_pcm snd_timer snd soundcore snd_page_alloc ipmi_si pcspkr psmouse ipmi_msghandler edac_core shpchp hpilo serio_raw hpwdt i5k_amb pci_hotplug joydev rng_core evdev c ontainer button processor ext4 jbd2 crc16 dm_mod raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear md_mod ext3 next3 mbcache jbd ses enclosure sd_m od crc_t10dif usbhid hid sg sr_mod cdrom ata_generic hpsa thermal ata_piix uhci_hcd mptspi scsi_transport_spi mptsas cciss libata bnx2 mptscsih mptbase ehci_hcd scsi_transport_sas scsi_mod thermal_sys usbcore nls_ base [last unloaded: scsi_wait_scan] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497345] Pid: 27670, comm: rsync Tainted: P 2.6.32-5-amd64 #1 Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497347] Call Trace: Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497355] [<ffffffffa018fd2b>] ? next3_snapshot_test_cow_bitmap+0x208/0x415 [next3] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497362] [<ffffffffa018fd2b>] ? next3_snapshot_test_cow_bitmap+0x208/0x415 [next3] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497368] [<ffffffff8104df9c>] ? warn_slowpath_common+0x77/0xa3 Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497375] [<ffffffffa018fd2b>] ? next3_snapshot_test_cow_bitmap+0x208/0x415 [next3] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497381] [<ffffffffa01693c9>] ? do_get_write_access+0x3e3/0x441 [jbd] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497389] [<ffffffffa01907ba>] ? next3_snapshot_test_and_cow+0x2ac/0x616 [next3] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497397] [<ffffffffa018f336>] ? __next3_journal_get_write_access_inode+0x40/0x8f [next3] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497404] [<ffffffffa017e33d>] ? next3_new_inode+0x4f5/0x9f1 [next3] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497409] [<ffffffffa0169ba0>] ? journal_start+0x96/0xc6 [jbd] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497416] [<ffffffffa01874a4>] ? next3_create+0x96/0x113 [next3] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497421] [<ffffffff810f6448>] ? generic_permission+0xe/0x8a Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497424] [<ffffffff810f7f44>] ? vfs_create+0x6d/0x89 Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497427] [<ffffffff810f8e6d>] ? do_filp_open+0x31e/0x94b Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497432] [<ffffffff810ed563>] ? do_sys_open+0x55/0xfc Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497436] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497438] ---[ end trace 90d840e343cd0075 ]--- Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497441] snapshot: failed to read COW bitmap #75360 of snapshot (36) Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497474] snapshot: next3_snapshot_get_write_access(b:1/75360) failed! h_ref=1, err=-5 Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497520] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497568] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 08:09:52 nl-gouda-07 kernel: [75987.499968] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 08:09:52 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc failed: Input/output error (5) Apr 26 08:09:52 nl-gouda-07 kernel: [75987.723775] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:53 nl-gouda-07 kernel: [75987.809208] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:10:03 nl-gouda-07 kernel: [75998.282167] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.925187] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970342] ------------[ cut here ]------------ Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970376] kernel BUG at /usr/src/next3-1.0.13/next3/snapshot.c:1063! Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970405] invalid opcode: 0000 [#1] SMP Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970434] last sysfs file: /sys/devices/pci0000:00/0000:00:02.0/0000:09:00.0/0000:0a:01.0/0000:0e:00.0/host3/port-3:0/end_device-3:0/target3:0:0/3:0:0:1/state Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970504] CPU 1 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970526] Modules linked in: hcpdriver(P) cpufreq_conservative cpufreq_powersave cpufreq_userspace cpufreq_stats dm_round_robin dm_multipath scsi_dh loop radeon ttm drm_kms _helper drm i2c_algo_bit i2c_core i5000_edac snd_pcm snd_timer snd soundcore snd_page_alloc ipmi_si pcspkr psmouse ipmi_msghandler edac_core shpchp hpilo serio_raw hpwdt i5k_amb pci_hotplug joydev rng_core evdev c ontainer button processor ext4 jbd2 crc16 dm_mod raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear md_mod ext3 next3 mbcache jbd ses enclosure sd_m od crc_t10dif usbhid hid sg sr_mod cdrom ata_generic hpsa thermal ata_piix uhci_hcd mptspi scsi_transport_spi mptsas cciss libata bnx2 mptscsih mptbase ehci_hcd scsi_transport_sas scsi_mod thermal_sys usbcore nls_ base [last unloaded: scsi_wait_scan] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970974] Pid: 27670, comm: rsync Tainted: P W 2.6.32-5-amd64 #1 ProLiant DL380 G5 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971020] RIP: 0010:[<ffffffffa0190335>] [<ffffffffa0190335>] next3_snapshot_test_and_move+0x8b/0x264 [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971081] RSP: 0018:ffff88012c541888 EFLAGS: 00010202 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971108] RAX: ffff88012b839000 RBX: 0000000000000000 RCX: 0000000082200883 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971138] RDX: ffff88010e39cba8 RSI: ffff8801289fc6f0 RDI: ffffffffa0197af0 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971168] RBP: ffff88010e39cba8 R08: 0000000000000001 R09: 0000000000000001 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971198] R10: 0000000000000004 R11: dead000000100100 R12: 0000000000000001 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971228] R13: ffff8801289fc6f0 R14: ffff88010e39cba8 R15: 0000000000000001 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971258] FS: 00007f82d6344700(0000) GS:ffff880005440000(0000) knlGS:0000000000000000 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971304] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971331] CR2: 00007fff137bd428 CR3: 000000012c534000 CR4: 00000000000006e0 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971361] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971391] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971422] Process rsync (pid: 27670, threadinfo ffff88012c540000, task ffff88012b918000) Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971475] Stack: Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971499] ffffffff81065058 0000000000001000 0000000082200883 ffffffffa0197af0 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971533] <0> ffff88012b838000 ffff88012c5419e8 0000000000000000 ffff880075670e00 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971585] <0> ffff880075670070 ffff88012c5419e8 ffff88010e39cba8 0000000000000004 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971653] Call Trace: Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971679] [<ffffffff81065058>] ? wake_bit_function+0x0/0x23 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971713] [<ffffffffa0181cf3>] ? next3_get_blocks_handle+0xc06/0x1127 [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971762] [<ffffffffa01825f3>] ? next3_getblk+0x53/0x172 [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971793] [<ffffffff8110da89>] ? __find_get_block+0x176/0x186 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971824] [<ffffffff810168f3>] ? read_tsc+0xa/0x20 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971855] [<ffffffffa018fd09>] ? next3_snapshot_test_cow_bitmap+0x1e6/0x415 [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971904] [<ffffffffa01693c9>] ? do_get_write_access+0x3e3/0x441 [jbd] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971936] [<ffffffff812fbf38>] ? __wait_on_bit+0x62/0x70 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971967] [<ffffffffa01907ba>] ? next3_snapshot_test_and_cow+0x2ac/0x616 [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972019] [<ffffffffa018f336>] ? __next3_journal_get_write_access_inode+0x40/0x8f [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972069] [<ffffffffa017e33d>] ? next3_new_inode+0x4f5/0x9f1 [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972101] [<ffffffffa0169ba0>] ? journal_start+0x96/0xc6 [jbd] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972133] [<ffffffffa01874a4>] ? next3_create+0x96/0x113 [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972163] [<ffffffff810f6448>] ? generic_permission+0xe/0x8a Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972192] [<ffffffff810f7f44>] ? vfs_create+0x6d/0x89 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972220] [<ffffffff810f8e6d>] ? do_filp_open+0x31e/0x94b Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972250] [<ffffffff810e6f20>] ? __slab_alloc+0xd3/0x39b Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972278] [<ffffffff810f9502>] ? getname+0x23/0x1a0 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972306] [<ffffffff810ed563>] ? do_sys_open+0x55/0xfc Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972334] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972361] 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 ef e8 8 3 f1 ff ff 31 c0 48 85 ed 74 68 0f b7 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972563] RIP [<ffffffffa0190335>] next3_snapshot_test_and_move+0x8b/0x264 [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972613] RSP <ffff88012c541888> Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972909] ---[ end trace 90d840e343cd0076 ]--- Apr 26 08:10:05 nl-gouda-07 rsyncd[27657]: rsync: connection unexpectedly closed (318 bytes received so far) [generator] Apr 26 08:10:05 nl-gouda-07 rsyncd[27657]: rsync error: error in rsync protocol data stream (code 12) at io.c(601) [generator=3.0.7] Regards, Kim. From: Amir Goldstein <ami...@gm...> To: Kim Hagen <kh...@mu...>, Cc: nex...@li... Date: 04/26/2012 06:56 PM Subject: Re: [Next3-users] Kernel bug.. Hi Kim, Did you see any other snapshot related errors/warning in the kernel log prior to this crash? Is this crash reproducible? What is the size of the volume/fs you are using? Have you been using this volume for a long time with snapshots? Can you please run fsck.next3 -nf to see if there are snapshot consistency errors on your fs. Thanks, Amir. On Thu, Apr 26, 2012 at 3:06 PM, Kim Hagen <kh...@mu...> wrote: Hi Amir, The kernel version is: root@nl-gouda-07:~# uname -a Linux nl-gouda-07 2.6.32-5-amd64 #1 SMP Thu Mar 22 17:26:33 UTC 2012 x86_64 GNU/Linux next3 version is: root@nl-gouda-07:~# next3 version snapshot-version = next3 snapshot v1.0.13-6 (2-May-2010) Kim From: Amir Goldstein <ami...@gm...> To: Kim Hagen <kh...@mu...>, Cc: nex...@li... Date: 04/26/2012 12:30 PM Subject: Re: [Next3-users] Kernel bug.. Hi Kim, Can you please specify kernel version (uname -a) and next3 version by Running 'next3 version ' command Thanks, Amir Sent from my private persona, enabled by Cellrox On Apr 26, 2012 12:45 PM, "Kim Hagen" <kh...@mu...> wrote: Hi, Im experiencing a kernel bug on making a snapshot, I really like to use next3 so i hope it can be fixed. >From what I can see rsync has something to do with it. I am using Debian Squeeze on a ProLiant DL380 G5, the file system is on top of an LVM volume on a multipath MSA2012sa device. [75999.970342] ------------[ cut here ]------------ [75999.970376] kernel BUG at /usr/src/next3-1.0.13/next3/snapshot.c:1063! [75999.970405] invalid opcode: 0000 [#1] SMP [75999.970434] last sysfs file: /sys/devices/pci0000:00/0000:00:02.0/0000:09:00.0/0000:0a:01.0/0000:0e:00.0/host3/port-3:0/end_device-3:0/target3:0:0/3:0:0:1/state [75999.970504] CPU 1 [75999.970526] Modules linked in: hcpdriver(P) cpufreq_conservative cpufreq_powersave cpufreq_userspace cpufreq_stats dm_round_robin dm_multipath scsi_dh loop radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core i5000_edac snd_pcm snd_timer snd soundcore snd_page_alloc ipmi_si pcspkr psmouse ipmi_msghandler edac_core shpchp hpilo serio_raw hpwdt i5k_amb pci_hotplug joydev rng_core evdev container button processor ext4 jbd2 crc16 dm_mod raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear md_mod ext3 next3 mbcache jbd ses enclosure sd_mod crc_t10dif usbhid hid sg sr_mod cdrom ata_generic hpsa thermal ata_piix uhci_hcd mptspi scsi_transport_spi mptsas cciss libata bnx2 mptscsih mptbase ehci_hcd scsi_transport_sas scsi_mod thermal_sys usbcore nls_base [last unloaded: scsi_wait_scan] [75999.970974] Pid: 27670, comm: rsync Tainted: P W 2.6.32-5-amd64 #1 ProLiant DL380 G5 [75999.971020] RIP: 0010:[<ffffffffa0190335>] [<ffffffffa0190335>] next3_snapshot_test_and_move+0x8b/0x264 [next3] [75999.971081] RSP: 0018:ffff88012c541888 EFLAGS: 00010202 [75999.971108] RAX: ffff88012b839000 RBX: 0000000000000000 RCX: 0000000082200883 [75999.971138] RDX: ffff88010e39cba8 RSI: ffff8801289fc6f0 RDI: ffffffffa0197af0 [75999.971168] RBP: ffff88010e39cba8 R08: 0000000000000001 R09: 0000000000000001 [75999.971198] R10: 0000000000000004 R11: dead000000100100 R12: 0000000000000001 [75999.971228] R13: ffff8801289fc6f0 R14: ffff88010e39cba8 R15: 0000000000000001 [75999.971258] FS: 00007f82d6344700(0000) GS:ffff880005440000(0000) knlGS:0000000000000000 [75999.971304] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b [75999.971331] CR2: 00007fff137bd428 CR3: 000000012c534000 CR4: 00000000000006e0 [75999.971361] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [75999.971391] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [75999.971422] Process rsync (pid: 27670, threadinfo ffff88012c540000, task ffff88012b918000) [75999.971475] Stack: [75999.971499] ffffffff81065058 0000000000001000 0000000082200883 ffffffffa0197af0 [75999.971533] <0> ffff88012b838000 ffff88012c5419e8 0000000000000000 ffff880075670e00 [75999.971585] <0> ffff880075670070 ffff88012c5419e8 ffff88010e39cba8 0000000000000004 [75999.971653] Call Trace: [75999.971679] [<ffffffff81065058>] ? wake_bit_function+0x0/0x23 [75999.971713] [<ffffffffa0181cf3>] ? next3_get_blocks_handle+0xc06/0x1127 [next3] [75999.971762] [<ffffffffa01825f3>] ? next3_getblk+0x53/0x172 [next3] [75999.971793] [<ffffffff8110da89>] ? __find_get_block+0x176/0x186 [75999.971824] [<ffffffff810168f3>] ? read_tsc+0xa/0x20 [75999.971855] [<ffffffffa018fd09>] ? next3_snapshot_test_cow_bitmap+0x1e6/0x415 [next3] [75999.971904] [<ffffffffa01693c9>] ? do_get_write_access+0x3e3/0x441 [jbd] [75999.971936] [<ffffffff812fbf38>] ? __wait_on_bit+0x62/0x70 [75999.971967] [<ffffffffa01907ba>] ? next3_snapshot_test_and_cow+0x2ac/0x616 [next3] [75999.972019] [<ffffffffa018f336>] ? __next3_journal_get_write_access_inode+0x40/0x8f [next3] [75999.972069] [<ffffffffa017e33d>] ? next3_new_inode+0x4f5/0x9f1 [next3] [75999.972101] [<ffffffffa0169ba0>] ? journal_start+0x96/0xc6 [jbd] [75999.972133] [<ffffffffa01874a4>] ? next3_create+0x96/0x113 [next3] [75999.972163] [<ffffffff810f6448>] ? generic_permission+0xe/0x8a [75999.972192] [<ffffffff810f7f44>] ? vfs_create+0x6d/0x89 [75999.972220] [<ffffffff810f8e6d>] ? do_filp_open+0x31e/0x94b [75999.972250] [<ffffffff810e6f20>] ? __slab_alloc+0xd3/0x39b [75999.972278] [<ffffffff810f9502>] ? getname+0x23/0x1a0 [75999.972306] [<ffffffff810ed563>] ? do_sys_open+0x55/0xfc [75999.972334] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b [75999.972361] 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 ef e8 83 f1 ff ff 31 c0 48 85 ed 74 68 0f b7 [75999.972563] RIP [<ffffffffa0190335>] next3_snapshot_test_and_move+0x8b/0x264 [next3] [75999.972613] RSP <ffff88012c541888> [75999.972909] ---[ end trace 90d840e343cd0076 ]--- Kind regards, Kim Hagen 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. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Next3-users mailing list Nex...@li... https://lists.sourceforge.net/lists/listinfo/next3-users 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. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Next3-users mailing list Nex...@li... https://lists.sourceforge.net/lists/listinfo/next3-users 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. 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. |
|
From: Amir G. <ami...@gm...> - 2012-04-27 11:25:27
|
Hi Kim, I see what the problem is. next3 version 1.0.13-6 had some bugs with regards to snapshot size > 4TB, which where resolved by this commit: https://github.com/amir73il/ext4-snapshots/commit/87a6639f2f440685d5a550b0ce759ad39e511e58 You need to upgrade to latest version 1.0.13-8 from Aug 2, 2011. Unfortunately, I seem to have neglected the next3 releases since I started releasing ext4-snapshots and this is the reason you did not get the latest next3 version when you installed it from the web site. I also did write any coherent documentation how to get the code from github and build the latests version. The Makefile used to create a release is in the next3-utils repository under patch directory: https://github.com/amir73il/next3-utils/blob/master/patch/Makefile If you like I can walk you through creating a new next3_snapshot.module.patch ('make next3_snapshot KERNEL=2.6.32') or you can wait until I clear some time to do it myself (and keep reminding me about it). Amir. On Fri, Apr 27, 2012 at 12:46 PM, Kim Hagen <kh...@mu...>wrote: > Hi Amir, > > The crash happens every day we create a snapshot it has happened for 3 > days straight. > > The size of our volume is 10TB. > > /dev/mapper/BackupData-BackupData 9.9T 478G 8.9T 5% > --- Logical volume --- > LV Name /dev/BackupData/BackupData > VG Name BackupData > LV UUID jndfk9-GYHb-6aqu-3MKV-fLml-OFd4-3qHJNg > LV Write Access read/write > LV Status available > # open 1 > LV Size 10.00 TiB > Current LE 2621440 > Segments 1 > Allocation inherit > Read ahead sectors auto > - currently set to 256 > Block device 253:1 > > > We have used this volume for 5 days, first 2 days were for testing > (without rsync) we also installed next3 at the same time we started using > the volume. > > The output of the fsck... (i had already removed the snapshot yesterday > and removed the cron job that takes the snapshots): > > # fsck.next3 -nf -C0 /dev/mapper/BackupData-BackupData > e2fsck 1.41.14-next3-1.0.13-1 (22-Feb-2011) > Pass 1: Checking inodes, blocks, and sizes > Pass 2: Checking directory structure > > Pass 3: Checking directory connectivity > > Pass 4: Checking reference counts > > Pass 5: Checking group summary information > > BackupData: 519307/671088640 files (3.7% non-contiguous), > 167287708/2684354560 blocks > > This is what is in the logs... (sorry for the length): > > Apr 26 07:00:02 nl-gouda-07 kernel: [71796.800005] snapshot: > next3_snapshot_enable() called with snapshot file (ino=21061634) not on list > Apr 26 07:00:02 nl-gouda-07 kernel: [71796.858621] snapshot: snapshot (36) > created > Apr 26 07:00:02 nl-gouda-07 kernel: [71797.094522] snapshot: snapshot (36) > activated > Apr 26 07:00:02 nl-gouda-07 kernel: [71797.096916] snapshot: snapshot (36) > has been taken > Apr 26 07:16:47 nl-gouda-07 kernel: [72802.630978] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:16:48 nl-gouda-07 kernel: [72803.712051] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:16:48 nl-gouda-07 kernel: [72803.773532] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:16:56 nl-gouda-07 kernel: [72810.923815] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:18:17 nl-gouda-07 kernel: [72892.729274] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:28:55 nl-gouda-07 kernel: [73530.588936] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:28:56 nl-gouda-07 kernel: [73530.839443] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:28:56 nl-gouda-07 kernel: [73531.517396] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:28:57 nl-gouda-07 kernel: [73532.444935] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:28:57 nl-gouda-07 kernel: [73532.491089] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:28:57 nl-gouda-07 kernel: [73532.758984] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:28:58 nl-gouda-07 kernel: [73533.479672] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:28:58 nl-gouda-07 kernel: [73533.747038] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:29:00 nl-gouda-07 kernel: [73535.182968] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:41:59 nl-gouda-07 kernel: [74314.708945] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:42:13 nl-gouda-07 kernel: [74328.253262] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:43:40 nl-gouda-07 kernel: [74415.359183] snapshot: > next3_snapshot_get_undo_access(b:0/67162) failed! h_ref=1, err=-5 > Apr 26 07:43:40 nl-gouda-07 kernel: [74415.359233] > next3_try_to_allocate_with_rsv: aborting transaction: IO failure in > __next3_journal_get_undo_access > Apr 26 07:43:40 nl-gouda-07 kernel: [74415.359283] NEXT3-fs error (device > dm-1) in next3_new_blocks: IO failure > Apr 26 07:43:40 nl-gouda-07 kernel: [74415.361688] NEXT3-fs error (device > dm-1) in next3_reserve_inode_write: Readonly filesystem > Apr 26 07:43:40 nl-gouda-07 kernel: [74415.363617] NEXT3-fs error (device > dm-1) in next3_dirty_inode: IO failure > Apr 26 07:43:40 nl-gouda-07 kernel: [74415.365512] NEXT3-fs error (device > dm-1) in next3_inode_list_add: Readonly filesystem > Apr 26 07:43:40 nl-gouda-07 kernel: [74415.367397] NEXT3-fs error (device > dm-1) in next3_write_begin: IO failure > Apr 26 07:43:40 nl-gouda-07 rsyncd[19142]: rsync: write failed on > "/de-duisburg-02/file.pdf.restore" (in BackupData): Input/output error (5) > Apr 26 07:43:40 nl-gouda-07 rsyncd[19142]: rsync error: error in file IO > (code 11) at receiver.c(302) [receiver=3.0.7] > Apr 26 07:43:40 nl-gouda-07 kernel: [74415.471732] snapshot: > next3_snapshot_get_undo_access(b:0/67162) failed! h_ref=2, err=-5 > Apr 26 07:43:40 nl-gouda-07 kernel: [74415.471781] > __next3_free_blocks_sb_inode: aborting transaction: IO failure in > __next3_journal_get_undo_access > Apr 26 07:43:40 nl-gouda-07 kernel: [74415.471831] NEXT3-fs error (device > dm-1) in __next3_free_blocks_sb_inode: IO failure > Apr 26 07:43:40 nl-gouda-07 kernel: [74415.474006] NEXT3-fs error (device > dm-1) in next3_reserve_inode_write: Readonly filesystem > Apr 26 07:43:40 nl-gouda-07 kernel: [74415.475918] NEXT3-fs error (device > dm-1) in next3_truncate: IO failure > Apr 26 07:43:40 nl-gouda-07 kernel: [74415.477827] NEXT3-fs error (device > dm-1) in next3_reserve_inode_write: Readonly filesystem > Apr 26 07:43:40 nl-gouda-07 kernel: [74415.479708] NEXT3-fs error (device > dm-1) in next3_inode_list_del: Readonly filesystem > Apr 26 07:43:40 nl-gouda-07 kernel: [74415.481625] NEXT3-fs error (device > dm-1) in next3_reserve_inode_write: Readonly filesystem > Apr 26 07:43:40 nl-gouda-07 kernel: [74415.483537] NEXT3-fs error (device > dm-1) in next3_delete_inode: IO failure > Apr 26 07:43:40 nl-gouda-07 rsyncd[19142]: rsync: connection unexpectedly > closed (1491 bytes received so far) [generator] > Apr 26 07:43:40 nl-gouda-07 rsyncd[19142]: rsync error: error in rsync > protocol data stream (code 12) at io.c(601) [generator=3.0.7] > Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638221] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638233] attempt to access > beyond end of device > Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638237] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638240] snapshot: failed to > read COW bitmap #67168 of snapshot (36) > Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638273] snapshot: > next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 > Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638319] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638380] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:46:59 nl-gouda-07 kernel: [74614.640734] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:00 nl-gouda-07 kernel: [74615.254942] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:47:00 nl-gouda-07 kernel: [74615.254953] attempt to access > beyond end of device > Apr 26 07:47:00 nl-gouda-07 kernel: [74615.254956] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:47:00 nl-gouda-07 kernel: [74615.254963] snapshot: failed to > read COW bitmap #67168 of snapshot (36) > Apr 26 07:47:00 nl-gouda-07 kernel: [74615.254995] snapshot: > next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 > Apr 26 07:47:00 nl-gouda-07 kernel: [74615.255041] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:47:00 nl-gouda-07 kernel: [74615.255089] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:47:00 nl-gouda-07 kernel: [74615.257408] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563027] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563037] attempt to access > beyond end of device > Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563041] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563044] snapshot: failed to > read COW bitmap #67168 of snapshot (36) > Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563077] snapshot: > next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 > Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563123] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563171] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:47:00 nl-gouda-07 kernel: [74615.566488] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839271] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839285] attempt to access > beyond end of device > Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839288] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839293] snapshot: failed to > read COW bitmap #67168 of snapshot (36) > Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839326] snapshot: > next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 > Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839372] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839421] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:47:01 nl-gouda-07 kernel: [74615.843553] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:03 nl-gouda-07 rsyslogd: [origin software="rsyslogd" > swVersion="4.6.4" x-pid="1841" x-info="http://www.rsyslog.com"] rsyslogd > was HUPed, type 'lightweight'. > Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302879] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302888] attempt to access > beyond end of device > Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302892] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302896] snapshot: failed to > read COW bitmap #67168 of snapshot (36) > Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302928] snapshot: > next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 > Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302975] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:47:05 nl-gouda-07 kernel: [74620.303023] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:47:05 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/......etc.Forum.pdf.fkslcK" (in BackupData) failed: > Input/output error (5) > Apr 26 07:47:05 nl-gouda-07 kernel: [74620.305387] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523632] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523641] attempt to access > beyond end of device > Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523645] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523649] snapshot: failed to > read COW bitmap #67168 of snapshot (36) > Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523681] snapshot: > next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 > Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523727] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523776] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:47:05 nl-gouda-07 kernel: [74620.525947] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:05 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/....etc.pdf.9RoRu9" (in BackupData) failed: Input/output > error (5) > Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355528] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355537] attempt to access > beyond end of device > Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355541] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355545] snapshot: failed to > read COW bitmap #67168 of snapshot (36) > Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355577] snapshot: > next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 > Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355632] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355681] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:47:06 nl-gouda-07 kernel: [74621.358001] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:06 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc.pdf.fUXwdB" (in BackupData) failed: Input/output > error (5) > Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451537] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451545] attempt to access > beyond end of device > Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451548] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451552] snapshot: failed to > read COW bitmap #67168 of snapshot (36) > Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451583] snapshot: > next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 > Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451630] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451678] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:47:06 nl-gouda-07 kernel: [74621.453915] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:06 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc.pdf.pmPwd3" (in BackupData) failed: Input/output > error (5) > Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899588] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899598] attempt to access > beyond end of device > Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899601] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899605] snapshot: failed to > read COW bitmap #67168 of snapshot (36) > Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899637] snapshot: > next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 > Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899683] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899731] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:47:07 nl-gouda-07 kernel: [74621.903637] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:07 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc.pdf.zWyoww" (in BackupData) failed: Input/output > error (5) > Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571597] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571607] attempt to access > beyond end of device > Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571610] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571614] snapshot: failed to > read COW bitmap #67168 of snapshot (36) > Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571646] snapshot: > next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 > Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571692] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571740] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:47:07 nl-gouda-07 kernel: [74622.574126] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:07 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc.pdf.ZeByM1" (in BackupData) failed: Input/output > error (5) > Apr 26 07:47:07 nl-gouda-07 kernel: [74622.739001] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:47:07 nl-gouda-07 kernel: [74622.739009] attempt to access > beyond end of device > Apr 26 07:47:07 nl-gouda-07 kernel: [74622.739013] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:47:07 nl-gouda-07 kernel: [74622.739017] snapshot: failed to > read COW bitmap #67168 of snapshot (36) > Apr 26 07:47:07 nl-gouda-07 kernel: [74622.745017] snapshot: > next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 > Apr 26 07:47:07 nl-gouda-07 kernel: [74622.745064] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:47:07 nl-gouda-07 kernel: [74622.745112] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:47:07 nl-gouda-07 kernel: [74622.747357] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:07 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc.1uWVwx" (in BackupData) failed: Input/output > error (5) > Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289794] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289802] attempt to access > beyond end of device > Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289805] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289809] snapshot: failed to > read COW bitmap #67169 of snapshot (36) > Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289841] snapshot: > next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 > Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289888] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289936] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:47:08 nl-gouda-07 kernel: [74623.292109] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:08 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc.pdf.dwNJO4" (in BackupData) failed: Input/output > error (5) > Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547394] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547405] attempt to access > beyond end of device > Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547409] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547413] snapshot: failed to > read COW bitmap #67169 of snapshot (36) > Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547445] snapshot: > next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 > Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547491] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547540] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:47:10 nl-gouda-07 kernel: [74625.550711] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:10 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc.pdf.xjB0JI" (in BackupData) failed: Input/output > error (5) > Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131379] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131389] attempt to access > beyond end of device > Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131393] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131397] snapshot: failed to > read COW bitmap #67169 of snapshot (36) > Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131429] snapshot: > next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 > Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131476] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131533] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:47:13 nl-gouda-07 kernel: [74628.134510] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:13 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc.pdf.loyFbu" (in BackupData) failed: Input/output > error (5) > Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386694] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386703] attempt to access > beyond end of device > Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386707] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386711] snapshot: failed to > read COW bitmap #67169 of snapshot (36) > Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386743] snapshot: > next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 > Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386789] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386837] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:47:15 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc.pdf.L8Mocm" (in BackupData) failed: Input/output > error (5) > Apr 26 07:47:15 nl-gouda-07 kernel: [74630.389213] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584440] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584452] attempt to access > beyond end of device > Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584455] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584460] snapshot: failed to > read COW bitmap #67169 of snapshot (36) > Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584492] snapshot: > next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 > Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584539] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584587] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:47:20 nl-gouda-07 kernel: [74635.587525] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:20 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc.pdf.DjEhlt" (in BackupData) failed: Input/output > error (5) > Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203074] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203085] attempt to access > beyond end of device > Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203088] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203093] snapshot: failed to > read COW bitmap #67169 of snapshot (36) > Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203126] snapshot: > next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 > Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203172] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203221] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:47:23 nl-gouda-07 kernel: [74638.207136] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:47:23 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc.pdf.BdBO6H" (in BackupData) failed: Input/output > error (5) > Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278241] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278249] attempt to access > beyond end of device > Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278253] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278257] snapshot: failed to > read COW bitmap #67171 of snapshot (36) > Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278289] snapshot: > next3_snapshot_get_write_access(b:1/67171) failed! h_ref=1, err=-5 > Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278335] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278383] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:48:57 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc.ls.Lj38Ce" (in BackupData) failed: Input/output > error (5) > Apr 26 07:48:57 nl-gouda-07 kernel: [74732.281008] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589644] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589654] attempt to access > beyond end of device > Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589657] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589661] snapshot: failed to > read COW bitmap #67174 of snapshot (36) > Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589694] snapshot: > next3_snapshot_get_write_access(b:1/67174) failed! h_ref=1, err=-5 > Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589740] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589788] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:50:10 nl-gouda-07 kernel: [74805.592176] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:50:10 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc (in BackupData) failed: Input/output error (5) > Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603200] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603207] attempt to access > beyond end of device > Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603210] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603214] snapshot: failed to > read COW bitmap #67174 of snapshot (36) > Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603246] snapshot: > next3_snapshot_get_write_access(b:1/67174) failed! h_ref=1, err=-5 > Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603298] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603347] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:50:10 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc.ls.NiNvWQ" (in BackupData) failed: Input/output > error (5) > Apr 26 07:50:10 nl-gouda-07 kernel: [74805.605316] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565081] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565091] attempt to access > beyond end of device > Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565094] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565098] snapshot: failed to > read COW bitmap #67173 of snapshot (36) > Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565131] snapshot: > next3_snapshot_get_write_access(b:1/67173) failed! h_ref=1, err=-5 > Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565177] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565225] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:50:43 nl-gouda-07 kernel: [74838.567610] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:50:43 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc.pdf.9NvFJ9" (in BackupData) failed: Input/output > error (5) > Apr 26 07:50:44 nl-gouda-07 kernel: [74838.797944] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:50:44 nl-gouda-07 kernel: [74838.797952] attempt to access > beyond end of device > Apr 26 07:50:44 nl-gouda-07 kernel: [74838.797955] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:50:44 nl-gouda-07 kernel: [74838.797959] snapshot: failed to > read COW bitmap #67173 of snapshot (36) > Apr 26 07:50:44 nl-gouda-07 kernel: [74838.797991] snapshot: > next3_snapshot_get_write_access(b:1/67173) failed! h_ref=1, err=-5 > Apr 26 07:50:44 nl-gouda-07 kernel: [74838.798037] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:50:44 nl-gouda-07 kernel: [74838.798085] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:50:44 nl-gouda-07 kernel: [74838.800157] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:50:44 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc failed: Input/output error (5) > Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802769] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802777] attempt to access > beyond end of device > Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802780] dm-1: rw=0, > want=23732295768, limit=21474836480 > Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802784] snapshot: failed to > read COW bitmap #67173 of snapshot (36) > Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802816] snapshot: > next3_snapshot_get_write_access(b:1/67173) failed! h_ref=1, err=-5 > Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802862] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802910] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 07:50:44 nl-gouda-07 kernel: [74838.805242] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 07:50:44 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc.ppt.hcFvdt" (in BackupData) failed: Input/output > error (5) > Apr 26 08:01:42 nl-gouda-07 kernel: [75497.760927] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 08:06:20 nl-gouda-07 kernel: [75774.795683] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 08:08:33 nl-gouda-07 kernel: [75907.799568] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 08:08:58 nl-gouda-07 kernel: [75933.145117] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 08:09:05 nl-gouda-07 kernel: [75939.889330] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 08:09:12 nl-gouda-07 kernel: [75947.223080] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 08:09:25 nl-gouda-07 kernel: [75960.531557] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 08:09:43 nl-gouda-07 kernel: [75978.034688] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 08:09:50 nl-gouda-07 kernel: [75985.114594] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 08:09:50 nl-gouda-07 kernel: [75985.296441] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497242] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497254] ------------[ cut here > ]------------ > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497275] WARNING: at > /usr/src/next3-1.0.13/next3/snapshot.c:486 > next3_snapshot_test_cow_bitmap+0x208/0x415 [next3]() > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497278] Hardware name: ProLiant > DL380 G5 > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497279] Modules linked in: > hcpdriver(P) cpufreq_conservative cpufreq_powersave cpufreq_userspace > cpufreq_stats dm_round_robin dm_multipath scsi_dh loop radeon ttm drm_kms > _helper drm i2c_algo_bit i2c_core i5000_edac snd_pcm snd_timer snd > soundcore snd_page_alloc ipmi_si pcspkr psmouse ipmi_msghandler edac_core > shpchp hpilo serio_raw hpwdt i5k_amb pci_hotplug joydev rng_core evdev c > ontainer button processor ext4 jbd2 crc16 dm_mod raid10 raid456 > async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx > raid1 raid0 multipath linear md_mod ext3 next3 mbcache jbd ses enclosure > sd_m > od crc_t10dif usbhid hid sg sr_mod cdrom ata_generic hpsa thermal ata_piix > uhci_hcd mptspi scsi_transport_spi mptsas cciss libata bnx2 mptscsih > mptbase ehci_hcd scsi_transport_sas scsi_mod thermal_sys usbcore nls_ > base [last unloaded: scsi_wait_scan] > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497345] Pid: 27670, comm: rsync > Tainted: P 2.6.32-5-amd64 #1 > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497347] Call Trace: > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497355] [<ffffffffa018fd2b>] ? > next3_snapshot_test_cow_bitmap+0x208/0x415 [next3] > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497362] [<ffffffffa018fd2b>] ? > next3_snapshot_test_cow_bitmap+0x208/0x415 [next3] > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497368] [<ffffffff8104df9c>] ? > warn_slowpath_common+0x77/0xa3 > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497375] [<ffffffffa018fd2b>] ? > next3_snapshot_test_cow_bitmap+0x208/0x415 [next3] > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497381] [<ffffffffa01693c9>] ? > do_get_write_access+0x3e3/0x441 [jbd] > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497389] [<ffffffffa01907ba>] ? > next3_snapshot_test_and_cow+0x2ac/0x616 [next3] > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497397] [<ffffffffa018f336>] ? > __next3_journal_get_write_access_inode+0x40/0x8f [next3] > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497404] [<ffffffffa017e33d>] ? > next3_new_inode+0x4f5/0x9f1 [next3] > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497409] [<ffffffffa0169ba0>] ? > journal_start+0x96/0xc6 [jbd] > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497416] [<ffffffffa01874a4>] ? > next3_create+0x96/0x113 [next3] > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497421] [<ffffffff810f6448>] ? > generic_permission+0xe/0x8a > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497424] [<ffffffff810f7f44>] ? > vfs_create+0x6d/0x89 > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497427] [<ffffffff810f8e6d>] ? > do_filp_open+0x31e/0x94b > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497432] [<ffffffff810ed563>] ? > do_sys_open+0x55/0xfc > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497436] [<ffffffff81010b42>] ? > system_call_fastpath+0x16/0x1b > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497438] ---[ end trace > 90d840e343cd0075 ]--- > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497441] snapshot: failed to > read COW bitmap #75360 of snapshot (36) > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497474] snapshot: > next3_snapshot_get_write_access(b:1/75360) failed! h_ref=1, err=-5 > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497520] next3_new_inode: > aborting transaction: IO failure in __next3_journal_get_write_access_inode > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497568] NEXT3-fs error (device > dm-1) in next3_new_inode: IO failure > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.499968] NEXT3-fs error (device > dm-1) in next3_create: IO failure > Apr 26 08:09:52 nl-gouda-07 rsyncd[27657]: rsync: mkstemp > "/de-duisburg-02/.....etc failed: Input/output error (5) > Apr 26 08:09:52 nl-gouda-07 kernel: [75987.723775] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 08:09:53 nl-gouda-07 kernel: [75987.809208] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 08:10:03 nl-gouda-07 kernel: [75998.282167] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.925187] NEXT3-fs warning > (device dm-1): next3_block_to_path: block < 0 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970342] ------------[ cut here > ]------------ > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970376] kernel BUG at > /usr/src/next3-1.0.13/next3/snapshot.c:1063! > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970405] invalid opcode: 0000 > [#1] SMP > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970434] last sysfs file: > /sys/devices/pci0000:00/0000:00:02.0/0000:09:00.0/0000:0a:01.0/0000:0e:00.0/host3/port-3:0/end_device-3:0/target3:0:0/3:0:0:1/state > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970504] CPU 1 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970526] Modules linked in: > hcpdriver(P) cpufreq_conservative cpufreq_powersave cpufreq_userspace > cpufreq_stats dm_round_robin dm_multipath scsi_dh loop radeon ttm drm_kms > _helper drm i2c_algo_bit i2c_core i5000_edac snd_pcm snd_timer snd > soundcore snd_page_alloc ipmi_si pcspkr psmouse ipmi_msghandler edac_core > shpchp hpilo serio_raw hpwdt i5k_amb pci_hotplug joydev rng_core evdev c > ontainer button processor ext4 jbd2 crc16 dm_mod raid10 raid456 > async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx > raid1 raid0 multipath linear md_mod ext3 next3 mbcache jbd ses enclosure > sd_m > od crc_t10dif usbhid hid sg sr_mod cdrom ata_generic hpsa thermal ata_piix > uhci_hcd mptspi scsi_transport_spi mptsas cciss libata bnx2 mptscsih > mptbase ehci_hcd scsi_transport_sas scsi_mod thermal_sys usbcore nls_ > base [last unloaded: scsi_wait_scan] > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970974] Pid: 27670, comm: rsync > Tainted: P W 2.6.32-5-amd64 #1 ProLiant DL380 G5 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971020] RIP: > 0010:[<ffffffffa0190335>] [<ffffffffa0190335>] > next3_snapshot_test_and_move+0x8b/0x264 [next3] > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971081] RSP: > 0018:ffff88012c541888 EFLAGS: 00010202 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971108] RAX: ffff88012b839000 > RBX: 0000000000000000 RCX: 0000000082200883 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971138] RDX: ffff88010e39cba8 > RSI: ffff8801289fc6f0 RDI: ffffffffa0197af0 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971168] RBP: ffff88010e39cba8 > R08: 0000000000000001 R09: 0000000000000001 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971198] R10: 0000000000000004 > R11: dead000000100100 R12: 0000000000000001 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971228] R13: ffff8801289fc6f0 > R14: ffff88010e39cba8 R15: 0000000000000001 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971258] FS: > 00007f82d6344700(0000) GS:ffff880005440000(0000) knlGS:0000000000000000 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971304] CS: 0010 DS: 0000 ES: > 0000 CR0: 000000008005003b > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971331] CR2: 00007fff137bd428 > CR3: 000000012c534000 CR4: 00000000000006e0 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971361] DR0: 0000000000000000 > DR1: 0000000000000000 DR2: 0000000000000000 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971391] DR3: 0000000000000000 > DR6: 00000000ffff0ff0 DR7: 0000000000000400 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971422] Process rsync (pid: > 27670, threadinfo ffff88012c540000, task ffff88012b918000) > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971475] Stack: > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971499] ffffffff81065058 > 0000000000001000 0000000082200883 ffffffffa0197af0 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971533] <0> ffff88012b838000 > ffff88012c5419e8 0000000000000000 ffff880075670e00 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971585] <0> ffff880075670070 > ffff88012c5419e8 ffff88010e39cba8 0000000000000004 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971653] Call Trace: > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971679] [<ffffffff81065058>] ? > wake_bit_function+0x0/0x23 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971713] [<ffffffffa0181cf3>] ? > next3_get_blocks_handle+0xc06/0x1127 [next3] > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971762] [<ffffffffa01825f3>] ? > next3_getblk+0x53/0x172 [next3] > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971793] [<ffffffff8110da89>] ? > __find_get_block+0x176/0x186 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971824] [<ffffffff810168f3>] ? > read_tsc+0xa/0x20 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971855] [<ffffffffa018fd09>] ? > next3_snapshot_test_cow_bitmap+0x1e6/0x415 [next3] > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971904] [<ffffffffa01693c9>] ? > do_get_write_access+0x3e3/0x441 [jbd] > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971936] [<ffffffff812fbf38>] ? > __wait_on_bit+0x62/0x70 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971967] [<ffffffffa01907ba>] ? > next3_snapshot_test_and_cow+0x2ac/0x616 [next3] > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972019] [<ffffffffa018f336>] ? > __next3_journal_get_write_access_inode+0x40/0x8f [next3] > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972069] [<ffffffffa017e33d>] ? > next3_new_inode+0x4f5/0x9f1 [next3] > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972101] [<ffffffffa0169ba0>] ? > journal_start+0x96/0xc6 [jbd] > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972133] [<ffffffffa01874a4>] ? > next3_create+0x96/0x113 [next3] > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972163] [<ffffffff810f6448>] ? > generic_permission+0xe/0x8a > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972192] [<ffffffff810f7f44>] ? > vfs_create+0x6d/0x89 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972220] [<ffffffff810f8e6d>] ? > do_filp_open+0x31e/0x94b > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972250] [<ffffffff810e6f20>] ? > __slab_alloc+0xd3/0x39b > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972278] [<ffffffff810f9502>] ? > getname+0x23/0x1a0 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972306] [<ffffffff810ed563>] ? > do_sys_open+0x55/0xfc > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972334] [<ffffffff81010b42>] ? > system_call_fastpath+0x16/0x1b > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972361] 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 ef e8 8 > 3 f1 ff ff 31 c0 48 85 ed 74 68 0f b7 > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972563] RIP > [<ffffffffa0190335>] next3_snapshot_test_and_move+0x8b/0x264 [next3] > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972613] RSP <ffff88012c541888> > Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972909] ---[ end trace > 90d840e343cd0076 ]--- > Apr 26 08:10:05 nl-gouda-07 rsyncd[27657]: rsync: connection unexpectedly > closed (318 bytes received so far) [generator] > Apr 26 08:10:05 nl-gouda-07 rsyncd[27657]: rsync error: error in rsync > protocol data stream (code 12) at io.c(601) [generator=3.0.7] > > > Regards, > > Kim. > > > > From: Amir Goldstein <ami...@gm...> > To: Kim Hagen <kh...@mu...>, > Cc: nex...@li... > Date: 04/26/2012 06:56 PM > Subject: Re: [Next3-users] Kernel bug.. > ------------------------------ > > > > Hi Kim, > > Did you see any other snapshot related errors/warning in the kernel log > prior to this crash? > > Is this crash reproducible? > > What is the size of the volume/fs you are using? > > Have you been using this volume for a long time with snapshots? > > Can you please run fsck.next3 -nf to see if there are snapshot consistency > errors on your fs. > > Thanks, > Amir. > > On Thu, Apr 26, 2012 at 3:06 PM, Kim Hagen <*kh...@mu...*<kh...@mu...>> > wrote: > Hi Amir, > > The kernel version is: > root@nl-gouda-07:~# uname -a > Linux nl-gouda-07 2.6.32-5-amd64 #1 SMP Thu Mar 22 17:26:33 UTC 2012 > x86_64 GNU/Linux > > next3 version is: > root@nl-gouda-07:~# next3 version > snapshot-version = next3 snapshot v1.0.13-6 (2-May-2010) > > > Kim > > > > > From: Amir Goldstein <*ami...@gm...* <ami...@gm...>> > To: Kim Hagen <*kh...@mu...*<kh...@mu...>>, > > Cc: *nex...@li...*<nex...@li...> > Date: 04/26/2012 12:30 PM > Subject: Re: [Next3-users] Kernel bug.. > ------------------------------ > > > > Hi Kim, > > Can you please specify kernel version (uname -a) and next3 version by > Running 'next3 version ' command > > Thanks, > Amir > > Sent from my private persona, enabled by Cellrox > > On Apr 26, 2012 12:45 PM, "Kim Hagen" <*kh...@mu...*<kh...@mu...>> > wrote: > Hi, > > Im experiencing a kernel bug on making a snapshot, I really like to use > next3 so i hope it can be fixed. > >From what I can see rsync has something to do with it. > > I am using Debian Squeeze on a ProLiant DL380 G5, > the file system is on top of an LVM volume on a multipath MSA2012sa > device. > > > [75999.970342] ------------[ cut here ]------------ > [75999.970376] kernel BUG at /usr/src/next3-1.0.13/next3/snapshot.c:1063! > [75999.970405] invalid opcode: 0000 [#1] SMP > [75999.970434] last sysfs file: > /sys/devices/pci0000:00/0000:00:02.0/0000:09:00.0/0000:0a:01.0/0000:0e:00.0/host3/port-3:0/end_device-3:0/target3:0:0/3:0:0:1/state > [75999.970504] CPU 1 > [75999.970526] Modules linked in: hcpdriver(P) cpufreq_conservative > cpufreq_powersave cpufreq_userspace cpufreq_stats dm_round_robin > dm_multipath scsi_dh loop radeon ttm drm_kms_helper drm i2c_algo_bit > i2c_core i5000_edac snd_pcm snd_timer snd soundcore snd_page_alloc ipmi_si > pcspkr psmouse ipmi_msghandler edac_core shpchp hpilo serio_raw hpwdt > i5k_amb pci_hotplug joydev rng_core evdev container button processor ext4 > jbd2 crc16 dm_mod raid10 raid456 async_raid6_recov async_pq raid6_pq > async_xor xor async_memcpy async_tx raid1 raid0 multipath linear md_mod > ext3 next3 mbcache jbd ses enclosure sd_mod crc_t10dif usbhid hid sg sr_mod > cdrom ata_generic hpsa thermal ata_piix uhci_hcd mptspi scsi_transport_spi > mptsas cciss libata bnx2 mptscsih mptbase ehci_hcd scsi_transport_sas > scsi_mod thermal_sys usbcore nls_base [last unloaded: scsi_wait_scan] > [75999.970974] Pid: 27670, comm: rsync Tainted: P W 2.6.32-5-amd64 > #1 ProLiant DL380 G5 > [75999.971020] RIP: 0010:[<ffffffffa0190335>] [<ffffffffa0190335>] > next3_snapshot_test_and_move+0x8b/0x264 [next3] > [75999.971081] RSP: 0018:ffff88012c541888 EFLAGS: 00010202 > [75999.971108] RAX: ffff88012b839000 RBX: 0000000000000000 RCX: > 0000000082200883 > [75999.971138] RDX: ffff88010e39cba8 RSI: ffff8801289fc6f0 RDI: > ffffffffa0197af0 > [75999.971168] RBP: ffff88010e39cba8 R08: 0000000000000001 R09: > 0000000000000001 > [75999.971198] R10: 0000000000000004 R11: dead000000100100 R12: > 0000000000000001 > [75999.971228] R13: ffff8801289fc6f0 R14: ffff88010e39cba8 R15: > 0000000000000001 > [75999.971258] FS: 00007f82d6344700(0000) GS:ffff880005440000(0000) > knlGS:0000000000000000 > [75999.971304] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b > [75999.971331] CR2: 00007fff137bd428 CR3: 000000012c534000 CR4: > 00000000000006e0 > [75999.971361] DR0: 0000000000000000 DR1: 0000000000000000 DR2: > 0000000000000000 > [75999.971391] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: > 0000000000000400 > [75999.971422] Process rsync (pid: 27670, threadinfo ffff88012c540000, > task ffff88012b918000) > [75999.971475] Stack: > [75999.971499] ffffffff81065058 0000000000001000 0000000082200883 > ffffffffa0197af0 > [75999.971533] <0> ffff88012b838000 ffff88012c5419e8 0000000000000000 > ffff880075670e00 > [75999.971585] <0> ffff880075670070 ffff88012c5419e8 ffff88010e39cba8 > 0000000000000004 > [75999.971653] Call Trace: > [75999.971679] [<ffffffff81065058>] ? wake_bit_function+0x0/0x23 > [75999.971713] [<ffffffffa0181cf3>] ? > next3_get_blocks_handle+0xc06/0x1127 [next3] > [75999.971762] [<ffffffffa01825f3>] ? next3_getblk+0x53/0x172 [next3] > [75999.971793] [<ffffffff8110da89>] ? __find_get_block+0x176/0x186 > [75999.971824] [<ffffffff810168f3>] ? read_tsc+0xa/0x20 > [75999.971855] [<ffffffffa018fd09>] ? > next3_snapshot_test_cow_bitmap+0x1e6/0x415 [next3] > [75999.971904] [<ffffffffa01693c9>] ? do_get_write_access+0x3e3/0x441 > [jbd] > [75999.971936] [<ffffffff812fbf38>] ? __wait_on_bit+0x62/0x70 > [75999.971967] [<ffffffffa01907ba>] ? > next3_snapshot_test_and_cow+0x2ac/0x616 [next3] > [75999.972019] [<ffffffffa018f336>] ? > __next3_journal_get_write_access_inode+0x40/0x8f [next3] > [75999.972069] [<ffffffffa017e33d>] ? next3_new_inode+0x4f5/0x9f1 [next3] > [75999.972101] [<ffffffffa0169ba0>] ? journal_start+0x96/0xc6 [jbd] > [75999.972133] [<ffffffffa01874a4>] ? next3_create+0x96/0x113 [next3] > [75999.972163] [<ffffffff810f6448>] ? generic_permission+0xe/0x8a > [75999.972192] [<ffffffff810f7f44>] ? vfs_create+0x6d/0x89 > [75999.972220] [<ffffffff810f8e6d>] ? do_filp_open+0x31e/0x94b > [75999.972250] [<ffffffff810e6f20>] ? __slab_alloc+0xd3/0x39b > [75999.972278] [<ffffffff810f9502>] ? getname+0x23/0x1a0 > [75999.972306] [<ffffffff810ed563>] ? do_sys_open+0x55/0xfc > [75999.972334] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b > [75999.972361] 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 ef e8 83 f1 ff ff 31 c0 48 85 ed 74 68 0f b7 > [75999.972563] RIP [<ffffffffa0190335>] > next3_snapshot_test_and_move+0x8b/0x264 [next3] > [75999.972613] RSP <ffff88012c541888> > [75999.972909] ---[ end trace 90d840e343cd0076 ]--- > > > Kind regards, > > Kim Hagen > > > > > > 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. > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. *http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/*<http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/> > _______________________________________________ > Next3-users mailing list* > **Nex...@li...* <Nex...@li...>* > **https://lists.sourceforge.net/lists/listinfo/next3-users*<https://lists.sourceforge.net/lists/listinfo/next3-users> > > > > > > > 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. > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. *http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/*<http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/> > _______________________________________________ > Next3-users mailing list* > **Nex...@li...* <Nex...@li...>* > **https://lists.sourceforge.net/lists/listinfo/next3-users*<https://lists.sourceforge.net/lists/listinfo/next3-users> > > > > > > > > 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. > > |
|
From: Kim H. <kh...@mu...> - 2012-04-27 09:46:30
|
Hi Amir, The crash happens every day we create a snapshot it has happened for 3 days straight. The size of our volume is 10TB. /dev/mapper/BackupData-BackupData 9.9T 478G 8.9T 5% --- Logical volume --- LV Name /dev/BackupData/BackupData VG Name BackupData LV UUID jndfk9-GYHb-6aqu-3MKV-fLml-OFd4-3qHJNg LV Write Access read/write LV Status available # open 1 LV Size 10.00 TiB Current LE 2621440 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 We have used this volume for 5 days, first 2 days were for testing (without rsync) we also installed next3 at the same time we started using the volume. The output of the fsck... (i had already removed the snapshot yesterday and removed the cron job that takes the snapshots): # fsck.next3 -nf -C0 /dev/mapper/BackupData-BackupData e2fsck 1.41.14-next3-1.0.13-1 (22-Feb-2011) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information BackupData: 519307/671088640 files (3.7% non-contiguous), 167287708/2684354560 blocks This is what is in the logs... (sorry for the length): Apr 26 07:00:02 nl-gouda-07 kernel: [71796.800005] snapshot: next3_snapshot_enable() called with snapshot file (ino=21061634) not on list Apr 26 07:00:02 nl-gouda-07 kernel: [71796.858621] snapshot: snapshot (36) created Apr 26 07:00:02 nl-gouda-07 kernel: [71797.094522] snapshot: snapshot (36) activated Apr 26 07:00:02 nl-gouda-07 kernel: [71797.096916] snapshot: snapshot (36) has been taken Apr 26 07:16:47 nl-gouda-07 kernel: [72802.630978] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:16:48 nl-gouda-07 kernel: [72803.712051] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:16:48 nl-gouda-07 kernel: [72803.773532] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:16:56 nl-gouda-07 kernel: [72810.923815] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:18:17 nl-gouda-07 kernel: [72892.729274] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:28:55 nl-gouda-07 kernel: [73530.588936] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:28:56 nl-gouda-07 kernel: [73530.839443] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:28:56 nl-gouda-07 kernel: [73531.517396] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:28:57 nl-gouda-07 kernel: [73532.444935] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:28:57 nl-gouda-07 kernel: [73532.491089] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:28:57 nl-gouda-07 kernel: [73532.758984] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:28:58 nl-gouda-07 kernel: [73533.479672] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:28:58 nl-gouda-07 kernel: [73533.747038] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:29:00 nl-gouda-07 kernel: [73535.182968] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:41:59 nl-gouda-07 kernel: [74314.708945] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:42:13 nl-gouda-07 kernel: [74328.253262] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:43:40 nl-gouda-07 kernel: [74415.359183] snapshot: next3_snapshot_get_undo_access(b:0/67162) failed! h_ref=1, err=-5 Apr 26 07:43:40 nl-gouda-07 kernel: [74415.359233] next3_try_to_allocate_with_rsv: aborting transaction: IO failure in __next3_journal_get_undo_access Apr 26 07:43:40 nl-gouda-07 kernel: [74415.359283] NEXT3-fs error (device dm-1) in next3_new_blocks: IO failure Apr 26 07:43:40 nl-gouda-07 kernel: [74415.361688] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem Apr 26 07:43:40 nl-gouda-07 kernel: [74415.363617] NEXT3-fs error (device dm-1) in next3_dirty_inode: IO failure Apr 26 07:43:40 nl-gouda-07 kernel: [74415.365512] NEXT3-fs error (device dm-1) in next3_inode_list_add: Readonly filesystem Apr 26 07:43:40 nl-gouda-07 kernel: [74415.367397] NEXT3-fs error (device dm-1) in next3_write_begin: IO failure Apr 26 07:43:40 nl-gouda-07 rsyncd[19142]: rsync: write failed on "/de-duisburg-02/file.pdf.restore" (in BackupData): Input/output error (5) Apr 26 07:43:40 nl-gouda-07 rsyncd[19142]: rsync error: error in file IO (code 11) at receiver.c(302) [receiver=3.0.7] Apr 26 07:43:40 nl-gouda-07 kernel: [74415.471732] snapshot: next3_snapshot_get_undo_access(b:0/67162) failed! h_ref=2, err=-5 Apr 26 07:43:40 nl-gouda-07 kernel: [74415.471781] __next3_free_blocks_sb_inode: aborting transaction: IO failure in __next3_journal_get_undo_access Apr 26 07:43:40 nl-gouda-07 kernel: [74415.471831] NEXT3-fs error (device dm-1) in __next3_free_blocks_sb_inode: IO failure Apr 26 07:43:40 nl-gouda-07 kernel: [74415.474006] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem Apr 26 07:43:40 nl-gouda-07 kernel: [74415.475918] NEXT3-fs error (device dm-1) in next3_truncate: IO failure Apr 26 07:43:40 nl-gouda-07 kernel: [74415.477827] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem Apr 26 07:43:40 nl-gouda-07 kernel: [74415.479708] NEXT3-fs error (device dm-1) in next3_inode_list_del: Readonly filesystem Apr 26 07:43:40 nl-gouda-07 kernel: [74415.481625] NEXT3-fs error (device dm-1) in next3_reserve_inode_write: Readonly filesystem Apr 26 07:43:40 nl-gouda-07 kernel: [74415.483537] NEXT3-fs error (device dm-1) in next3_delete_inode: IO failure Apr 26 07:43:40 nl-gouda-07 rsyncd[19142]: rsync: connection unexpectedly closed (1491 bytes received so far) [generator] Apr 26 07:43:40 nl-gouda-07 rsyncd[19142]: rsync error: error in rsync protocol data stream (code 12) at io.c(601) [generator=3.0.7] Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638221] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638233] attempt to access beyond end of device Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638237] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638240] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638273] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638319] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:46:59 nl-gouda-07 kernel: [74614.638380] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:46:59 nl-gouda-07 kernel: [74614.640734] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:00 nl-gouda-07 kernel: [74615.254942] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:00 nl-gouda-07 kernel: [74615.254953] attempt to access beyond end of device Apr 26 07:47:00 nl-gouda-07 kernel: [74615.254956] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:00 nl-gouda-07 kernel: [74615.254963] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:00 nl-gouda-07 kernel: [74615.254995] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:00 nl-gouda-07 kernel: [74615.255041] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:00 nl-gouda-07 kernel: [74615.255089] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:00 nl-gouda-07 kernel: [74615.257408] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563027] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563037] attempt to access beyond end of device Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563041] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563044] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563077] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563123] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:00 nl-gouda-07 kernel: [74615.563171] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:00 nl-gouda-07 kernel: [74615.566488] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839271] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839285] attempt to access beyond end of device Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839288] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839293] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839326] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839372] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:01 nl-gouda-07 kernel: [74615.839421] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:01 nl-gouda-07 kernel: [74615.843553] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:03 nl-gouda-07 rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="1841" x-info="http://www.rsyslog.com"] rsyslogd was HUPed, type 'lightweight'. Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302879] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302888] attempt to access beyond end of device Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302892] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302896] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302928] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:05 nl-gouda-07 kernel: [74620.302975] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:05 nl-gouda-07 kernel: [74620.303023] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:05 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/......etc.Forum.pdf.fkslcK" (in BackupData) failed: Input/output error (5) Apr 26 07:47:05 nl-gouda-07 kernel: [74620.305387] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523632] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523641] attempt to access beyond end of device Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523645] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523649] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523681] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523727] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:05 nl-gouda-07 kernel: [74620.523776] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:05 nl-gouda-07 kernel: [74620.525947] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:05 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/....etc.pdf.9RoRu9" (in BackupData) failed: Input/output error (5) Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355528] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355537] attempt to access beyond end of device Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355541] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355545] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355577] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355632] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:06 nl-gouda-07 kernel: [74621.355681] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:06 nl-gouda-07 kernel: [74621.358001] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:06 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.fUXwdB" (in BackupData) failed: Input/output error (5) Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451537] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451545] attempt to access beyond end of device Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451548] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451552] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451583] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451630] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:06 nl-gouda-07 kernel: [74621.451678] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:06 nl-gouda-07 kernel: [74621.453915] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:06 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.pmPwd3" (in BackupData) failed: Input/output error (5) Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899588] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899598] attempt to access beyond end of device Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899601] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899605] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899637] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899683] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:07 nl-gouda-07 kernel: [74621.899731] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:07 nl-gouda-07 kernel: [74621.903637] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:07 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.zWyoww" (in BackupData) failed: Input/output error (5) Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571597] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571607] attempt to access beyond end of device Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571610] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571614] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571646] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571692] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:07 nl-gouda-07 kernel: [74622.571740] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:07 nl-gouda-07 kernel: [74622.574126] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:07 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.ZeByM1" (in BackupData) failed: Input/output error (5) Apr 26 07:47:07 nl-gouda-07 kernel: [74622.739001] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:07 nl-gouda-07 kernel: [74622.739009] attempt to access beyond end of device Apr 26 07:47:07 nl-gouda-07 kernel: [74622.739013] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:07 nl-gouda-07 kernel: [74622.739017] snapshot: failed to read COW bitmap #67168 of snapshot (36) Apr 26 07:47:07 nl-gouda-07 kernel: [74622.745017] snapshot: next3_snapshot_get_write_access(b:1/67168) failed! h_ref=1, err=-5 Apr 26 07:47:07 nl-gouda-07 kernel: [74622.745064] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:07 nl-gouda-07 kernel: [74622.745112] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:07 nl-gouda-07 kernel: [74622.747357] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:07 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.1uWVwx" (in BackupData) failed: Input/output error (5) Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289794] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289802] attempt to access beyond end of device Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289805] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289809] snapshot: failed to read COW bitmap #67169 of snapshot (36) Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289841] snapshot: next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289888] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:08 nl-gouda-07 kernel: [74623.289936] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:08 nl-gouda-07 kernel: [74623.292109] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:08 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.dwNJO4" (in BackupData) failed: Input/output error (5) Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547394] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547405] attempt to access beyond end of device Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547409] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547413] snapshot: failed to read COW bitmap #67169 of snapshot (36) Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547445] snapshot: next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547491] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:10 nl-gouda-07 kernel: [74625.547540] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:10 nl-gouda-07 kernel: [74625.550711] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:10 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.xjB0JI" (in BackupData) failed: Input/output error (5) Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131379] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131389] attempt to access beyond end of device Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131393] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131397] snapshot: failed to read COW bitmap #67169 of snapshot (36) Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131429] snapshot: next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131476] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:13 nl-gouda-07 kernel: [74628.131533] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:13 nl-gouda-07 kernel: [74628.134510] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:13 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.loyFbu" (in BackupData) failed: Input/output error (5) Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386694] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386703] attempt to access beyond end of device Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386707] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386711] snapshot: failed to read COW bitmap #67169 of snapshot (36) Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386743] snapshot: next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386789] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:15 nl-gouda-07 kernel: [74630.386837] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:15 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.L8Mocm" (in BackupData) failed: Input/output error (5) Apr 26 07:47:15 nl-gouda-07 kernel: [74630.389213] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584440] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584452] attempt to access beyond end of device Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584455] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584460] snapshot: failed to read COW bitmap #67169 of snapshot (36) Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584492] snapshot: next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584539] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:20 nl-gouda-07 kernel: [74635.584587] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:20 nl-gouda-07 kernel: [74635.587525] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:20 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.DjEhlt" (in BackupData) failed: Input/output error (5) Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203074] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203085] attempt to access beyond end of device Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203088] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203093] snapshot: failed to read COW bitmap #67169 of snapshot (36) Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203126] snapshot: next3_snapshot_get_write_access(b:1/67169) failed! h_ref=1, err=-5 Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203172] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:47:23 nl-gouda-07 kernel: [74638.203221] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:47:23 nl-gouda-07 kernel: [74638.207136] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:47:23 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.BdBO6H" (in BackupData) failed: Input/output error (5) Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278241] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278249] attempt to access beyond end of device Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278253] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278257] snapshot: failed to read COW bitmap #67171 of snapshot (36) Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278289] snapshot: next3_snapshot_get_write_access(b:1/67171) failed! h_ref=1, err=-5 Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278335] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:48:57 nl-gouda-07 kernel: [74732.278383] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:48:57 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.ls.Lj38Ce" (in BackupData) failed: Input/output error (5) Apr 26 07:48:57 nl-gouda-07 kernel: [74732.281008] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589644] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589654] attempt to access beyond end of device Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589657] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589661] snapshot: failed to read COW bitmap #67174 of snapshot (36) Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589694] snapshot: next3_snapshot_get_write_access(b:1/67174) failed! h_ref=1, err=-5 Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589740] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:50:10 nl-gouda-07 kernel: [74805.589788] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:50:10 nl-gouda-07 kernel: [74805.592176] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:50:10 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc (in BackupData) failed: Input/output error (5) Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603200] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603207] attempt to access beyond end of device Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603210] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603214] snapshot: failed to read COW bitmap #67174 of snapshot (36) Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603246] snapshot: next3_snapshot_get_write_access(b:1/67174) failed! h_ref=1, err=-5 Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603298] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:50:10 nl-gouda-07 kernel: [74805.603347] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:50:10 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.ls.NiNvWQ" (in BackupData) failed: Input/output error (5) Apr 26 07:50:10 nl-gouda-07 kernel: [74805.605316] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565081] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565091] attempt to access beyond end of device Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565094] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565098] snapshot: failed to read COW bitmap #67173 of snapshot (36) Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565131] snapshot: next3_snapshot_get_write_access(b:1/67173) failed! h_ref=1, err=-5 Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565177] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:50:43 nl-gouda-07 kernel: [74838.565225] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:50:43 nl-gouda-07 kernel: [74838.567610] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:50:43 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.pdf.9NvFJ9" (in BackupData) failed: Input/output error (5) Apr 26 07:50:44 nl-gouda-07 kernel: [74838.797944] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:50:44 nl-gouda-07 kernel: [74838.797952] attempt to access beyond end of device Apr 26 07:50:44 nl-gouda-07 kernel: [74838.797955] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:50:44 nl-gouda-07 kernel: [74838.797959] snapshot: failed to read COW bitmap #67173 of snapshot (36) Apr 26 07:50:44 nl-gouda-07 kernel: [74838.797991] snapshot: next3_snapshot_get_write_access(b:1/67173) failed! h_ref=1, err=-5 Apr 26 07:50:44 nl-gouda-07 kernel: [74838.798037] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:50:44 nl-gouda-07 kernel: [74838.798085] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:50:44 nl-gouda-07 kernel: [74838.800157] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:50:44 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc failed: Input/output error (5) Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802769] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802777] attempt to access beyond end of device Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802780] dm-1: rw=0, want=23732295768, limit=21474836480 Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802784] snapshot: failed to read COW bitmap #67173 of snapshot (36) Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802816] snapshot: next3_snapshot_get_write_access(b:1/67173) failed! h_ref=1, err=-5 Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802862] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 07:50:44 nl-gouda-07 kernel: [74838.802910] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 07:50:44 nl-gouda-07 kernel: [74838.805242] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 07:50:44 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc.ppt.hcFvdt" (in BackupData) failed: Input/output error (5) Apr 26 08:01:42 nl-gouda-07 kernel: [75497.760927] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:06:20 nl-gouda-07 kernel: [75774.795683] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:08:33 nl-gouda-07 kernel: [75907.799568] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:08:58 nl-gouda-07 kernel: [75933.145117] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:05 nl-gouda-07 kernel: [75939.889330] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:12 nl-gouda-07 kernel: [75947.223080] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:25 nl-gouda-07 kernel: [75960.531557] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:43 nl-gouda-07 kernel: [75978.034688] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:50 nl-gouda-07 kernel: [75985.114594] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:50 nl-gouda-07 kernel: [75985.296441] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497242] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497254] ------------[ cut here ]------------ Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497275] WARNING: at /usr/src/next3-1.0.13/next3/snapshot.c:486 next3_snapshot_test_cow_bitmap+0x208/0x415 [next3]() Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497278] Hardware name: ProLiant DL380 G5 Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497279] Modules linked in: hcpdriver(P) cpufreq_conservative cpufreq_powersave cpufreq_userspace cpufreq_stats dm_round_robin dm_multipath scsi_dh loop radeon ttm drm_kms _helper drm i2c_algo_bit i2c_core i5000_edac snd_pcm snd_timer snd soundcore snd_page_alloc ipmi_si pcspkr psmouse ipmi_msghandler edac_core shpchp hpilo serio_raw hpwdt i5k_amb pci_hotplug joydev rng_core evdev c ontainer button processor ext4 jbd2 crc16 dm_mod raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear md_mod ext3 next3 mbcache jbd ses enclosure sd_m od crc_t10dif usbhid hid sg sr_mod cdrom ata_generic hpsa thermal ata_piix uhci_hcd mptspi scsi_transport_spi mptsas cciss libata bnx2 mptscsih mptbase ehci_hcd scsi_transport_sas scsi_mod thermal_sys usbcore nls_ base [last unloaded: scsi_wait_scan] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497345] Pid: 27670, comm: rsync Tainted: P 2.6.32-5-amd64 #1 Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497347] Call Trace: Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497355] [<ffffffffa018fd2b>] ? next3_snapshot_test_cow_bitmap+0x208/0x415 [next3] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497362] [<ffffffffa018fd2b>] ? next3_snapshot_test_cow_bitmap+0x208/0x415 [next3] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497368] [<ffffffff8104df9c>] ? warn_slowpath_common+0x77/0xa3 Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497375] [<ffffffffa018fd2b>] ? next3_snapshot_test_cow_bitmap+0x208/0x415 [next3] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497381] [<ffffffffa01693c9>] ? do_get_write_access+0x3e3/0x441 [jbd] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497389] [<ffffffffa01907ba>] ? next3_snapshot_test_and_cow+0x2ac/0x616 [next3] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497397] [<ffffffffa018f336>] ? __next3_journal_get_write_access_inode+0x40/0x8f [next3] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497404] [<ffffffffa017e33d>] ? next3_new_inode+0x4f5/0x9f1 [next3] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497409] [<ffffffffa0169ba0>] ? journal_start+0x96/0xc6 [jbd] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497416] [<ffffffffa01874a4>] ? next3_create+0x96/0x113 [next3] Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497421] [<ffffffff810f6448>] ? generic_permission+0xe/0x8a Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497424] [<ffffffff810f7f44>] ? vfs_create+0x6d/0x89 Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497427] [<ffffffff810f8e6d>] ? do_filp_open+0x31e/0x94b Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497432] [<ffffffff810ed563>] ? do_sys_open+0x55/0xfc Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497436] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497438] ---[ end trace 90d840e343cd0075 ]--- Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497441] snapshot: failed to read COW bitmap #75360 of snapshot (36) Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497474] snapshot: next3_snapshot_get_write_access(b:1/75360) failed! h_ref=1, err=-5 Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497520] next3_new_inode: aborting transaction: IO failure in __next3_journal_get_write_access_inode Apr 26 08:09:52 nl-gouda-07 kernel: [75987.497568] NEXT3-fs error (device dm-1) in next3_new_inode: IO failure Apr 26 08:09:52 nl-gouda-07 kernel: [75987.499968] NEXT3-fs error (device dm-1) in next3_create: IO failure Apr 26 08:09:52 nl-gouda-07 rsyncd[27657]: rsync: mkstemp "/de-duisburg-02/.....etc failed: Input/output error (5) Apr 26 08:09:52 nl-gouda-07 kernel: [75987.723775] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:09:53 nl-gouda-07 kernel: [75987.809208] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:10:03 nl-gouda-07 kernel: [75998.282167] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.925187] NEXT3-fs warning (device dm-1): next3_block_to_path: block < 0 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970342] ------------[ cut here ]------------ Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970376] kernel BUG at /usr/src/next3-1.0.13/next3/snapshot.c:1063! Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970405] invalid opcode: 0000 [#1] SMP Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970434] last sysfs file: /sys/devices/pci0000:00/0000:00:02.0/0000:09:00.0/0000:0a:01.0/0000:0e:00.0/host3/port-3:0/end_device-3:0/target3:0:0/3:0:0:1/state Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970504] CPU 1 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970526] Modules linked in: hcpdriver(P) cpufreq_conservative cpufreq_powersave cpufreq_userspace cpufreq_stats dm_round_robin dm_multipath scsi_dh loop radeon ttm drm_kms _helper drm i2c_algo_bit i2c_core i5000_edac snd_pcm snd_timer snd soundcore snd_page_alloc ipmi_si pcspkr psmouse ipmi_msghandler edac_core shpchp hpilo serio_raw hpwdt i5k_amb pci_hotplug joydev rng_core evdev c ontainer button processor ext4 jbd2 crc16 dm_mod raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear md_mod ext3 next3 mbcache jbd ses enclosure sd_m od crc_t10dif usbhid hid sg sr_mod cdrom ata_generic hpsa thermal ata_piix uhci_hcd mptspi scsi_transport_spi mptsas cciss libata bnx2 mptscsih mptbase ehci_hcd scsi_transport_sas scsi_mod thermal_sys usbcore nls_ base [last unloaded: scsi_wait_scan] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.970974] Pid: 27670, comm: rsync Tainted: P W 2.6.32-5-amd64 #1 ProLiant DL380 G5 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971020] RIP: 0010:[<ffffffffa0190335>] [<ffffffffa0190335>] next3_snapshot_test_and_move+0x8b/0x264 [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971081] RSP: 0018:ffff88012c541888 EFLAGS: 00010202 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971108] RAX: ffff88012b839000 RBX: 0000000000000000 RCX: 0000000082200883 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971138] RDX: ffff88010e39cba8 RSI: ffff8801289fc6f0 RDI: ffffffffa0197af0 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971168] RBP: ffff88010e39cba8 R08: 0000000000000001 R09: 0000000000000001 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971198] R10: 0000000000000004 R11: dead000000100100 R12: 0000000000000001 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971228] R13: ffff8801289fc6f0 R14: ffff88010e39cba8 R15: 0000000000000001 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971258] FS: 00007f82d6344700(0000) GS:ffff880005440000(0000) knlGS:0000000000000000 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971304] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971331] CR2: 00007fff137bd428 CR3: 000000012c534000 CR4: 00000000000006e0 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971361] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971391] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971422] Process rsync (pid: 27670, threadinfo ffff88012c540000, task ffff88012b918000) Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971475] Stack: Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971499] ffffffff81065058 0000000000001000 0000000082200883 ffffffffa0197af0 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971533] <0> ffff88012b838000 ffff88012c5419e8 0000000000000000 ffff880075670e00 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971585] <0> ffff880075670070 ffff88012c5419e8 ffff88010e39cba8 0000000000000004 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971653] Call Trace: Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971679] [<ffffffff81065058>] ? wake_bit_function+0x0/0x23 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971713] [<ffffffffa0181cf3>] ? next3_get_blocks_handle+0xc06/0x1127 [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971762] [<ffffffffa01825f3>] ? next3_getblk+0x53/0x172 [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971793] [<ffffffff8110da89>] ? __find_get_block+0x176/0x186 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971824] [<ffffffff810168f3>] ? read_tsc+0xa/0x20 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971855] [<ffffffffa018fd09>] ? next3_snapshot_test_cow_bitmap+0x1e6/0x415 [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971904] [<ffffffffa01693c9>] ? do_get_write_access+0x3e3/0x441 [jbd] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971936] [<ffffffff812fbf38>] ? __wait_on_bit+0x62/0x70 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.971967] [<ffffffffa01907ba>] ? next3_snapshot_test_and_cow+0x2ac/0x616 [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972019] [<ffffffffa018f336>] ? __next3_journal_get_write_access_inode+0x40/0x8f [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972069] [<ffffffffa017e33d>] ? next3_new_inode+0x4f5/0x9f1 [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972101] [<ffffffffa0169ba0>] ? journal_start+0x96/0xc6 [jbd] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972133] [<ffffffffa01874a4>] ? next3_create+0x96/0x113 [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972163] [<ffffffff810f6448>] ? generic_permission+0xe/0x8a Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972192] [<ffffffff810f7f44>] ? vfs_create+0x6d/0x89 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972220] [<ffffffff810f8e6d>] ? do_filp_open+0x31e/0x94b Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972250] [<ffffffff810e6f20>] ? __slab_alloc+0xd3/0x39b Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972278] [<ffffffff810f9502>] ? getname+0x23/0x1a0 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972306] [<ffffffff810ed563>] ? do_sys_open+0x55/0xfc Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972334] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972361] 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 ef e8 8 3 f1 ff ff 31 c0 48 85 ed 74 68 0f b7 Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972563] RIP [<ffffffffa0190335>] next3_snapshot_test_and_move+0x8b/0x264 [next3] Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972613] RSP <ffff88012c541888> Apr 26 08:10:05 nl-gouda-07 kernel: [75999.972909] ---[ end trace 90d840e343cd0076 ]--- Apr 26 08:10:05 nl-gouda-07 rsyncd[27657]: rsync: connection unexpectedly closed (318 bytes received so far) [generator] Apr 26 08:10:05 nl-gouda-07 rsyncd[27657]: rsync error: error in rsync protocol data stream (code 12) at io.c(601) [generator=3.0.7] Regards, Kim. From: Amir Goldstein <ami...@gm...> To: Kim Hagen <kh...@mu...>, Cc: nex...@li... Date: 04/26/2012 06:56 PM Subject: Re: [Next3-users] Kernel bug.. Hi Kim, Did you see any other snapshot related errors/warning in the kernel log prior to this crash? Is this crash reproducible? What is the size of the volume/fs you are using? Have you been using this volume for a long time with snapshots? Can you please run fsck.next3 -nf to see if there are snapshot consistency errors on your fs. Thanks, Amir. On Thu, Apr 26, 2012 at 3:06 PM, Kim Hagen <kh...@mu...> wrote: Hi Amir, The kernel version is: root@nl-gouda-07:~# uname -a Linux nl-gouda-07 2.6.32-5-amd64 #1 SMP Thu Mar 22 17:26:33 UTC 2012 x86_64 GNU/Linux next3 version is: root@nl-gouda-07:~# next3 version snapshot-version = next3 snapshot v1.0.13-6 (2-May-2010) Kim From: Amir Goldstein <ami...@gm...> To: Kim Hagen <kh...@mu...>, Cc: nex...@li... Date: 04/26/2012 12:30 PM Subject: Re: [Next3-users] Kernel bug.. Hi Kim, Can you please specify kernel version (uname -a) and next3 version by Running 'next3 version ' command Thanks, Amir Sent from my private persona, enabled by Cellrox On Apr 26, 2012 12:45 PM, "Kim Hagen" <kh...@mu...> wrote: Hi, Im experiencing a kernel bug on making a snapshot, I really like to use next3 so i hope it can be fixed. >From what I can see rsync has something to do with it. I am using Debian Squeeze on a ProLiant DL380 G5, the file system is on top of an LVM volume on a multipath MSA2012sa device. [75999.970342] ------------[ cut here ]------------ [75999.970376] kernel BUG at /usr/src/next3-1.0.13/next3/snapshot.c:1063! [75999.970405] invalid opcode: 0000 [#1] SMP [75999.970434] last sysfs file: /sys/devices/pci0000:00/0000:00:02.0/0000:09:00.0/0000:0a:01.0/0000:0e:00.0/host3/port-3:0/end_device-3:0/target3:0:0/3:0:0:1/state [75999.970504] CPU 1 [75999.970526] Modules linked in: hcpdriver(P) cpufreq_conservative cpufreq_powersave cpufreq_userspace cpufreq_stats dm_round_robin dm_multipath scsi_dh loop radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core i5000_edac snd_pcm snd_timer snd soundcore snd_page_alloc ipmi_si pcspkr psmouse ipmi_msghandler edac_core shpchp hpilo serio_raw hpwdt i5k_amb pci_hotplug joydev rng_core evdev container button processor ext4 jbd2 crc16 dm_mod raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear md_mod ext3 next3 mbcache jbd ses enclosure sd_mod crc_t10dif usbhid hid sg sr_mod cdrom ata_generic hpsa thermal ata_piix uhci_hcd mptspi scsi_transport_spi mptsas cciss libata bnx2 mptscsih mptbase ehci_hcd scsi_transport_sas scsi_mod thermal_sys usbcore nls_base [last unloaded: scsi_wait_scan] [75999.970974] Pid: 27670, comm: rsync Tainted: P W 2.6.32-5-amd64 #1 ProLiant DL380 G5 [75999.971020] RIP: 0010:[<ffffffffa0190335>] [<ffffffffa0190335>] next3_snapshot_test_and_move+0x8b/0x264 [next3] [75999.971081] RSP: 0018:ffff88012c541888 EFLAGS: 00010202 [75999.971108] RAX: ffff88012b839000 RBX: 0000000000000000 RCX: 0000000082200883 [75999.971138] RDX: ffff88010e39cba8 RSI: ffff8801289fc6f0 RDI: ffffffffa0197af0 [75999.971168] RBP: ffff88010e39cba8 R08: 0000000000000001 R09: 0000000000000001 [75999.971198] R10: 0000000000000004 R11: dead000000100100 R12: 0000000000000001 [75999.971228] R13: ffff8801289fc6f0 R14: ffff88010e39cba8 R15: 0000000000000001 [75999.971258] FS: 00007f82d6344700(0000) GS:ffff880005440000(0000) knlGS:0000000000000000 [75999.971304] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b [75999.971331] CR2: 00007fff137bd428 CR3: 000000012c534000 CR4: 00000000000006e0 [75999.971361] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [75999.971391] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [75999.971422] Process rsync (pid: 27670, threadinfo ffff88012c540000, task ffff88012b918000) [75999.971475] Stack: [75999.971499] ffffffff81065058 0000000000001000 0000000082200883 ffffffffa0197af0 [75999.971533] <0> ffff88012b838000 ffff88012c5419e8 0000000000000000 ffff880075670e00 [75999.971585] <0> ffff880075670070 ffff88012c5419e8 ffff88010e39cba8 0000000000000004 [75999.971653] Call Trace: [75999.971679] [<ffffffff81065058>] ? wake_bit_function+0x0/0x23 [75999.971713] [<ffffffffa0181cf3>] ? next3_get_blocks_handle+0xc06/0x1127 [next3] [75999.971762] [<ffffffffa01825f3>] ? next3_getblk+0x53/0x172 [next3] [75999.971793] [<ffffffff8110da89>] ? __find_get_block+0x176/0x186 [75999.971824] [<ffffffff810168f3>] ? read_tsc+0xa/0x20 [75999.971855] [<ffffffffa018fd09>] ? next3_snapshot_test_cow_bitmap+0x1e6/0x415 [next3] [75999.971904] [<ffffffffa01693c9>] ? do_get_write_access+0x3e3/0x441 [jbd] [75999.971936] [<ffffffff812fbf38>] ? __wait_on_bit+0x62/0x70 [75999.971967] [<ffffffffa01907ba>] ? next3_snapshot_test_and_cow+0x2ac/0x616 [next3] [75999.972019] [<ffffffffa018f336>] ? __next3_journal_get_write_access_inode+0x40/0x8f [next3] [75999.972069] [<ffffffffa017e33d>] ? next3_new_inode+0x4f5/0x9f1 [next3] [75999.972101] [<ffffffffa0169ba0>] ? journal_start+0x96/0xc6 [jbd] [75999.972133] [<ffffffffa01874a4>] ? next3_create+0x96/0x113 [next3] [75999.972163] [<ffffffff810f6448>] ? generic_permission+0xe/0x8a [75999.972192] [<ffffffff810f7f44>] ? vfs_create+0x6d/0x89 [75999.972220] [<ffffffff810f8e6d>] ? do_filp_open+0x31e/0x94b [75999.972250] [<ffffffff810e6f20>] ? __slab_alloc+0xd3/0x39b [75999.972278] [<ffffffff810f9502>] ? getname+0x23/0x1a0 [75999.972306] [<ffffffff810ed563>] ? do_sys_open+0x55/0xfc [75999.972334] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b [75999.972361] 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 ef e8 83 f1 ff ff 31 c0 48 85 ed 74 68 0f b7 [75999.972563] RIP [<ffffffffa0190335>] next3_snapshot_test_and_move+0x8b/0x264 [next3] [75999.972613] RSP <ffff88012c541888> [75999.972909] ---[ end trace 90d840e343cd0076 ]--- Kind regards, Kim Hagen 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. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Next3-users mailing list Nex...@li... https://lists.sourceforge.net/lists/listinfo/next3-users 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. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Next3-users mailing list Nex...@li... https://lists.sourceforge.net/lists/listinfo/next3-users 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. |
|
From: Amir G. <ami...@gm...> - 2012-04-26 16:56:35
|
Hi Kim, Did you see any other snapshot related errors/warning in the kernel log prior to this crash? Is this crash reproducible? What is the size of the volume/fs you are using? Have you been using this volume for a long time with snapshots? Can you please run fsck.next3 -nf to see if there are snapshot consistency errors on your fs. Thanks, Amir. On Thu, Apr 26, 2012 at 3:06 PM, Kim Hagen <kh...@mu...>wrote: > Hi Amir, > > The kernel version is: > root@nl-gouda-07:~# uname -a > Linux nl-gouda-07 2.6.32-5-amd64 #1 SMP Thu Mar 22 17:26:33 UTC 2012 > x86_64 GNU/Linux > > next3 version is: > root@nl-gouda-07:~# next3 version > snapshot-version = next3 snapshot v1.0.13-6 (2-May-2010) > > > Kim > > > > > From: Amir Goldstein <ami...@gm...> > To: Kim Hagen <kh...@mu...>, > Cc: nex...@li... > Date: 04/26/2012 12:30 PM > Subject: Re: [Next3-users] Kernel bug.. > ------------------------------ > > > > Hi Kim, > > Can you please specify kernel version (uname -a) and next3 version by > Running 'next3 version ' command > > Thanks, > Amir > > Sent from my private persona, enabled by Cellrox > > On Apr 26, 2012 12:45 PM, "Kim Hagen" <*kh...@mu...*<kh...@mu...>> > wrote: > Hi, > > Im experiencing a kernel bug on making a snapshot, I really like to use > next3 so i hope it can be fixed. > >From what I can see rsync has something to do with it. > > I am using Debian Squeeze on a ProLiant DL380 G5, > the file system is on top of an LVM volume on a multipath MSA2012sa > device. > > > [75999.970342] ------------[ cut here ]------------ > [75999.970376] kernel BUG at /usr/src/next3-1.0.13/next3/snapshot.c:1063! > [75999.970405] invalid opcode: 0000 [#1] SMP > [75999.970434] last sysfs file: > /sys/devices/pci0000:00/0000:00:02.0/0000:09:00.0/0000:0a:01.0/0000:0e:00.0/host3/port-3:0/end_device-3:0/target3:0:0/3:0:0:1/state > [75999.970504] CPU 1 > [75999.970526] Modules linked in: hcpdriver(P) cpufreq_conservative > cpufreq_powersave cpufreq_userspace cpufreq_stats dm_round_robin > dm_multipath scsi_dh loop radeon ttm drm_kms_helper drm i2c_algo_bit > i2c_core i5000_edac snd_pcm snd_timer snd soundcore snd_page_alloc ipmi_si > pcspkr psmouse ipmi_msghandler edac_core shpchp hpilo serio_raw hpwdt > i5k_amb pci_hotplug joydev rng_core evdev container button processor ext4 > jbd2 crc16 dm_mod raid10 raid456 async_raid6_recov async_pq raid6_pq > async_xor xor async_memcpy async_tx raid1 raid0 multipath linear md_mod > ext3 next3 mbcache jbd ses enclosure sd_mod crc_t10dif usbhid hid sg sr_mod > cdrom ata_generic hpsa thermal ata_piix uhci_hcd mptspi scsi_transport_spi > mptsas cciss libata bnx2 mptscsih mptbase ehci_hcd scsi_transport_sas > scsi_mod thermal_sys usbcore nls_base [last unloaded: scsi_wait_scan] > [75999.970974] Pid: 27670, comm: rsync Tainted: P W 2.6.32-5-amd64 > #1 ProLiant DL380 G5 > [75999.971020] RIP: 0010:[<ffffffffa0190335>] [<ffffffffa0190335>] > next3_snapshot_test_and_move+0x8b/0x264 [next3] > [75999.971081] RSP: 0018:ffff88012c541888 EFLAGS: 00010202 > [75999.971108] RAX: ffff88012b839000 RBX: 0000000000000000 RCX: > 0000000082200883 > [75999.971138] RDX: ffff88010e39cba8 RSI: ffff8801289fc6f0 RDI: > ffffffffa0197af0 > [75999.971168] RBP: ffff88010e39cba8 R08: 0000000000000001 R09: > 0000000000000001 > [75999.971198] R10: 0000000000000004 R11: dead000000100100 R12: > 0000000000000001 > [75999.971228] R13: ffff8801289fc6f0 R14: ffff88010e39cba8 R15: > 0000000000000001 > [75999.971258] FS: 00007f82d6344700(0000) GS:ffff880005440000(0000) > knlGS:0000000000000000 > [75999.971304] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b > [75999.971331] CR2: 00007fff137bd428 CR3: 000000012c534000 CR4: > 00000000000006e0 > [75999.971361] DR0: 0000000000000000 DR1: 0000000000000000 DR2: > 0000000000000000 > [75999.971391] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: > 0000000000000400 > [75999.971422] Process rsync (pid: 27670, threadinfo ffff88012c540000, > task ffff88012b918000) > [75999.971475] Stack: > [75999.971499] ffffffff81065058 0000000000001000 0000000082200883 > ffffffffa0197af0 > [75999.971533] <0> ffff88012b838000 ffff88012c5419e8 0000000000000000 > ffff880075670e00 > [75999.971585] <0> ffff880075670070 ffff88012c5419e8 ffff88010e39cba8 > 0000000000000004 > [75999.971653] Call Trace: > [75999.971679] [<ffffffff81065058>] ? wake_bit_function+0x0/0x23 > [75999.971713] [<ffffffffa0181cf3>] ? > next3_get_blocks_handle+0xc06/0x1127 [next3] > [75999.971762] [<ffffffffa01825f3>] ? next3_getblk+0x53/0x172 [next3] > [75999.971793] [<ffffffff8110da89>] ? __find_get_block+0x176/0x186 > [75999.971824] [<ffffffff810168f3>] ? read_tsc+0xa/0x20 > [75999.971855] [<ffffffffa018fd09>] ? > next3_snapshot_test_cow_bitmap+0x1e6/0x415 [next3] > [75999.971904] [<ffffffffa01693c9>] ? do_get_write_access+0x3e3/0x441 > [jbd] > [75999.971936] [<ffffffff812fbf38>] ? __wait_on_bit+0x62/0x70 > [75999.971967] [<ffffffffa01907ba>] ? > next3_snapshot_test_and_cow+0x2ac/0x616 [next3] > [75999.972019] [<ffffffffa018f336>] ? > __next3_journal_get_write_access_inode+0x40/0x8f [next3] > [75999.972069] [<ffffffffa017e33d>] ? next3_new_inode+0x4f5/0x9f1 [next3] > [75999.972101] [<ffffffffa0169ba0>] ? journal_start+0x96/0xc6 [jbd] > [75999.972133] [<ffffffffa01874a4>] ? next3_create+0x96/0x113 [next3] > [75999.972163] [<ffffffff810f6448>] ? generic_permission+0xe/0x8a > [75999.972192] [<ffffffff810f7f44>] ? vfs_create+0x6d/0x89 > [75999.972220] [<ffffffff810f8e6d>] ? do_filp_open+0x31e/0x94b > [75999.972250] [<ffffffff810e6f20>] ? __slab_alloc+0xd3/0x39b > [75999.972278] [<ffffffff810f9502>] ? getname+0x23/0x1a0 > [75999.972306] [<ffffffff810ed563>] ? do_sys_open+0x55/0xfc > [75999.972334] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b > [75999.972361] 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 ef e8 83 f1 ff ff 31 c0 48 85 ed 74 68 0f b7 > [75999.972563] RIP [<ffffffffa0190335>] > next3_snapshot_test_and_move+0x8b/0x264 [next3] > [75999.972613] RSP <ffff88012c541888> > [75999.972909] ---[ end trace 90d840e343cd0076 ]--- > > > Kind regards, > > Kim Hagen > > > > > > 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. > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. *http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/*<http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/> > _______________________________________________ > Next3-users mailing list* > **Nex...@li...* <Nex...@li...>* > **https://lists.sourceforge.net/lists/listinfo/next3-users*<https://lists.sourceforge.net/lists/listinfo/next3-users> > > > > > > > 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. > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Next3-users mailing list > Nex...@li... > https://lists.sourceforge.net/lists/listinfo/next3-users > > |
|
From: Kim H. <kh...@mu...> - 2012-04-26 12:06:37
|
Hi Amir, The kernel version is: root@nl-gouda-07:~# uname -a Linux nl-gouda-07 2.6.32-5-amd64 #1 SMP Thu Mar 22 17:26:33 UTC 2012 x86_64 GNU/Linux next3 version is: root@nl-gouda-07:~# next3 version snapshot-version = next3 snapshot v1.0.13-6 (2-May-2010) Kim From: Amir Goldstein <ami...@gm...> To: Kim Hagen <kh...@mu...>, Cc: nex...@li... Date: 04/26/2012 12:30 PM Subject: Re: [Next3-users] Kernel bug.. Hi Kim, Can you please specify kernel version (uname -a) and next3 version by Running 'next3 version ' command Thanks, Amir Sent from my private persona, enabled by Cellrox On Apr 26, 2012 12:45 PM, "Kim Hagen" <kh...@mu...> wrote: Hi, Im experiencing a kernel bug on making a snapshot, I really like to use next3 so i hope it can be fixed. >From what I can see rsync has something to do with it. I am using Debian Squeeze on a ProLiant DL380 G5, the file system is on top of an LVM volume on a multipath MSA2012sa device. [75999.970342] ------------[ cut here ]------------ [75999.970376] kernel BUG at /usr/src/next3-1.0.13/next3/snapshot.c:1063! [75999.970405] invalid opcode: 0000 [#1] SMP [75999.970434] last sysfs file: /sys/devices/pci0000:00/0000:00:02.0/0000:09:00.0/0000:0a:01.0/0000:0e:00.0/host3/port-3:0/end_device-3:0/target3:0:0/3:0:0:1/state [75999.970504] CPU 1 [75999.970526] Modules linked in: hcpdriver(P) cpufreq_conservative cpufreq_powersave cpufreq_userspace cpufreq_stats dm_round_robin dm_multipath scsi_dh loop radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core i5000_edac snd_pcm snd_timer snd soundcore snd_page_alloc ipmi_si pcspkr psmouse ipmi_msghandler edac_core shpchp hpilo serio_raw hpwdt i5k_amb pci_hotplug joydev rng_core evdev container button processor ext4 jbd2 crc16 dm_mod raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear md_mod ext3 next3 mbcache jbd ses enclosure sd_mod crc_t10dif usbhid hid sg sr_mod cdrom ata_generic hpsa thermal ata_piix uhci_hcd mptspi scsi_transport_spi mptsas cciss libata bnx2 mptscsih mptbase ehci_hcd scsi_transport_sas scsi_mod thermal_sys usbcore nls_base [last unloaded: scsi_wait_scan] [75999.970974] Pid: 27670, comm: rsync Tainted: P W 2.6.32-5-amd64 #1 ProLiant DL380 G5 [75999.971020] RIP: 0010:[<ffffffffa0190335>] [<ffffffffa0190335>] next3_snapshot_test_and_move+0x8b/0x264 [next3] [75999.971081] RSP: 0018:ffff88012c541888 EFLAGS: 00010202 [75999.971108] RAX: ffff88012b839000 RBX: 0000000000000000 RCX: 0000000082200883 [75999.971138] RDX: ffff88010e39cba8 RSI: ffff8801289fc6f0 RDI: ffffffffa0197af0 [75999.971168] RBP: ffff88010e39cba8 R08: 0000000000000001 R09: 0000000000000001 [75999.971198] R10: 0000000000000004 R11: dead000000100100 R12: 0000000000000001 [75999.971228] R13: ffff8801289fc6f0 R14: ffff88010e39cba8 R15: 0000000000000001 [75999.971258] FS: 00007f82d6344700(0000) GS:ffff880005440000(0000) knlGS:0000000000000000 [75999.971304] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b [75999.971331] CR2: 00007fff137bd428 CR3: 000000012c534000 CR4: 00000000000006e0 [75999.971361] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [75999.971391] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 [75999.971422] Process rsync (pid: 27670, threadinfo ffff88012c540000, task ffff88012b918000) [75999.971475] Stack: [75999.971499] ffffffff81065058 0000000000001000 0000000082200883 ffffffffa0197af0 [75999.971533] <0> ffff88012b838000 ffff88012c5419e8 0000000000000000 ffff880075670e00 [75999.971585] <0> ffff880075670070 ffff88012c5419e8 ffff88010e39cba8 0000000000000004 [75999.971653] Call Trace: [75999.971679] [<ffffffff81065058>] ? wake_bit_function+0x0/0x23 [75999.971713] [<ffffffffa0181cf3>] ? next3_get_blocks_handle+0xc06/0x1127 [next3] [75999.971762] [<ffffffffa01825f3>] ? next3_getblk+0x53/0x172 [next3] [75999.971793] [<ffffffff8110da89>] ? __find_get_block+0x176/0x186 [75999.971824] [<ffffffff810168f3>] ? read_tsc+0xa/0x20 [75999.971855] [<ffffffffa018fd09>] ? next3_snapshot_test_cow_bitmap+0x1e6/0x415 [next3] [75999.971904] [<ffffffffa01693c9>] ? do_get_write_access+0x3e3/0x441 [jbd] [75999.971936] [<ffffffff812fbf38>] ? __wait_on_bit+0x62/0x70 [75999.971967] [<ffffffffa01907ba>] ? next3_snapshot_test_and_cow+0x2ac/0x616 [next3] [75999.972019] [<ffffffffa018f336>] ? __next3_journal_get_write_access_inode+0x40/0x8f [next3] [75999.972069] [<ffffffffa017e33d>] ? next3_new_inode+0x4f5/0x9f1 [next3] [75999.972101] [<ffffffffa0169ba0>] ? journal_start+0x96/0xc6 [jbd] [75999.972133] [<ffffffffa01874a4>] ? next3_create+0x96/0x113 [next3] [75999.972163] [<ffffffff810f6448>] ? generic_permission+0xe/0x8a [75999.972192] [<ffffffff810f7f44>] ? vfs_create+0x6d/0x89 [75999.972220] [<ffffffff810f8e6d>] ? do_filp_open+0x31e/0x94b [75999.972250] [<ffffffff810e6f20>] ? __slab_alloc+0xd3/0x39b [75999.972278] [<ffffffff810f9502>] ? getname+0x23/0x1a0 [75999.972306] [<ffffffff810ed563>] ? do_sys_open+0x55/0xfc [75999.972334] [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b [75999.972361] 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 ef e8 83 f1 ff ff 31 c0 48 85 ed 74 68 0f b7 [75999.972563] RIP [<ffffffffa0190335>] next3_snapshot_test_and_move+0x8b/0x264 [next3] [75999.972613] RSP <ffff88012c541888> [75999.972909] ---[ end trace 90d840e343cd0076 ]--- Kind regards, Kim Hagen 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. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Next3-users mailing list Nex...@li... https://lists.sourceforge.net/lists/listinfo/next3-users 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. |
1 message has been excluded from this view by a project administrator.
