next3-devel Mailing List for NEXT3
Brought to you by:
amir73il
Menu
▾
▴
next3-devel — Next3 development and bug reports
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
(4) |
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
(12) |
Feb
(12) |
Mar
(8) |
Apr
(1) |
May
(2) |
Jun
(25) |
Jul
(31) |
Aug
(2) |
Sep
(13) |
Oct
(63) |
Nov
(10) |
Dec
(2) |
| 2012 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
(5) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: SUSE <ev...@su...> - 2022-03-02 16:17:34
|
To view this email as a web page, go to the following address: https://more.suse.com/index.php/email/emailWebview?mkt_tok=OTM3LURDSC0yNjEAAAGC6lbO_lgXfw9h_Vs9R2AXKJEJsHbuqmEXPXW6dFHqVEVOPi5MT921FVRvq3EcgmILXlR7aQqIo0ZJEmlpEY9EfLdar2fJf6pS057MejvEi1T4&md_id=11064 Seis etapas para agilidad y continuidad Sepa como una modernización de TI segura puede ayudarle a mantenerse competitivo en un periodo de cambios y disrupciones aceleradas. ¿Qué está incluido? Descubra con este infográfico como puede entregar agilidad y continuidad mientras abraza la innovación. Usted verá en este infográfico: - Seis etapas sencillas para guiarle hacia una estrategia que entregue agilidad y continuidad de negocios. - Como usar su equipo, procesos y tecnologías para construir la base de una infraestructura de TI estable y adaptable. - El papel do código abierto en la modernización de TI segura. Solicitar una llamada <https://em.suse.com/OTM3LURDSC0yNjEAAAGC6lbO_Wv5HHA60NVln8fJAjAWCgrqreqfRHWqfvASKXAziftC6HdnaZKYJ1iXjvNuzdE9o_c=> Copyright © 2022 SUSE, Todos los derechos reservados.| Cancelar suscripción <[[https://more.suse.com/UnsubscribePage.html?mkt_unsubscribe=1&mkt_tok=OTM3LURDSC0yNjEAAAGC6lbO_lgXfw9h_Vs9R2AXKJEJsHbuqmEXPXW6dFHqVEVOPi5MT921FVRvq3EcgmILXlR7aQqIo0ZJEmlpEY9EfLdar2fJf6pS057MejvEi1T4]]> SUSE Software Solutions Germany GmbH | Maxfeldstr. 5 | 90409 Nürnberg | Germany | HRB 36809 Usted está recibiendo esta comunicación de marketing de SUSE porque ha optado por recibir comunicaciones anteriormente o porque creemos haber un motivo comercial legítimo para entrar en contacto con usted a respecto de los productos y servicios SUSE. Visite la página Gerenciamiento de Suscripción SUSE <https://em.suse.com/OTM3LURDSC0yNjEAAAGC6lbO_a1J0cD8OLRKKjHX6N4IV5z48aQTsuVBT9657W8UQIaNbdtQv3iDaGUDZm1z8WivqhM=> si desea recusar otras notificaciones. Todas las marcas registradas de terceros son propiedad de sus respectivas empresas. |
|
From: Tania S. <ev...@su...> - 2020-05-27 12:41:21
|
<[[https://more.suse.com/index.php/email/emailWebview?mkt_tok=eyJpIjoiT0dFeU16ZzVPV0k0T1RNNSIsInQiOiJHL3ZsYkhsSUQyTk5pa0NISUZzd3BiM3lIYnRhckZyMEhrZjRyWXV3ZG52NXgwQUZmOHFIM3BOZU4wR1BSRUZodjdGNWtqb0ppZGwvcXYyQVM5Y3RzM005OS9OVVFhTDhxRkJCOTBnZXljL2JkQUVLMml1ZThUcXgyMHlzOWNtMiJ9]]> WEBINAR: 28.05.2020 | 10.00 Uhr Nonstop-IT sicherstellen Die Bereitstellung einer unterbrechungsfreien IT bedeutet, dass Ihr Unternehmen sich darauf verlassen kann, dass Infrastruktur, Systeme und Menschen zur Verfügung stehen, wenn sie gebraucht werden. Serviceunterbrechungen können den Ruf Ihres Unternehmens und Ihren Kundendienst negativ beeinträchtigen. Aus diesem Grund sollte die Ausführung, Behebung und Anpassung Ihrer Systeme ohne damit verbundener Ausfälle für Sie Priorität haben. SUSE bietet hochverfügbare IT-Lösungen dank konvergenter Infrastruktur mit geschäftskritischem Linux und skalierbarer Automatisierung. Um das wichtige Ziel einer ständigen Verfügbarkeit von Services zu unterstützen, können Sie Anwendungsdaten clusterübergreifend replizieren, sodass sie schneller wiederhergestellt werden können. Zudem bieten wir Ihnen die Möglichkeit, Kernel-Fixes und Systemaktualisierungen ohne Unterbrechung Ihres Service anzuwenden, damit Sie besser auf sich ändernde Marktbedingungen reagieren und gleichzeitig die Sicherheit Ihres Systems gewährleisten können. Interessiert? Melden Sie sich jetzt <https://em.suse.com/F7EC700PG0D0d3yj000HVPc>zu unserem Live-Webinar an und erfahren Sie, wie Sie sofort mit der Umsetzung starten können! Webinar WEBINAR: Nonstop-IT sicherstellen DATUM: 28. Mai 2020 UHRZEIT: 10.00 - 11.00 Uhr SPRECHER: Jörg Bunse, Sales Engineer SUSE Rückruf anfordern <https://em.suse.com/o03EP00ux007dD0cEHCVj70> |
|
From: Amir G. <ami...@gm...> - 2013-01-30 10:25:37
|
Hi Manik, I am not sure exactly what information you are missing. you should be able to find most information in Next3 wiki. for example, API to delete snapshot: http://sourceforge.net/apps/mediawiki/next3/index.php?title=User-kernel_API#Deleting_a_snapshot and stages of deleting snapshot: http://sourceforge.net/apps/mediawiki/next3/index.php?title=Technical_overview#Snapshot_delete If you let me know what you are missing, maybe I can help to clarify. Amir. On Sun, Jan 27, 2013 at 8:20 AM, Manik Mhangare <man...@su... > wrote: > 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. > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnnow-d2d > _______________________________________________ > Next3-users mailing list > Nex...@li... > https://lists.sourceforge.net/lists/listinfo/next3-users > > |
|
From: SUSE
<in...@su...> - 2012-06-11 19:18:57
|
If your email program has trouble displaying this email, view it as a web page http://now.eloqua.com/es.asp?s=1163&e=159429&elq=72799a34ea89498c98a960e63b1d125b -------------------------------------- SUSECon 2012 After twenty years of delivering the world's best enterprise Linux technology, SUSE opens registration for the first annual global conference for SUSE customers, partners and community enthusiasts - SUSECon. SUSECon will take place September 18-21, at the Caribe Royale Hotel in Orlando, Florida. The conference will feature technical and business presentations, demonstrations, hands-on labs, training, industry partner technology showcases, customer case studies and keynotes from industry experts. SUSECon sessions will give you engineering insights and directions, customer case studies, partner solutions, hands-on training and road-map disclosures. No matter what your technical level is, you will learn more about enterprise computing, cloud computing and Linux management technologies. Sessions will be presented in tracks that will include: *Cloud deployments *Deployment of mission-critical Linux systems *High performance computing *Heterogeneity & interoperability *Linux management *Virtualization Specific session topics will include: *High availability *Performance optimization *Secure Shell *SUSE Linux Enterprise Server analysis *Using btrfs, Snapshot/Rollback *Technology Roadmaps *and much, much more... Register today! <http://app.mktg.novell.com/e/er?s=1163&lid=5999&elq=72799a34ea89498c98a960e63b1d125b> Special Pricing! <http://app.mktg.novell.com/e/er?s=1163&lid=5999&elq=72799a34ea89498c98a960e63b1d125b> Event Details ------------- Location: Caribe Royale Hotel Orlando, Florida Date: 18-21 September, 2012 Price: Early Bird - $699 USD The first 25 people to register for SUSECon will receive a limited edition numbered-series SUSE jacket. Immortalize yourself as one of the first people to ever attend SUSECon! "" SUSE <http://www.suse.com> Copyright © 2011 SUSE, All rights reserved. All third party trademarks are the property of their respective owners. This email is sent only to registered subscribers. Please click this link to manage your email preferences. <http://www.suse.com/company/subscribe/?&id=CNVLL000002184356&em=nex...@li...&elq=72799a34ea89498c98a960e63b1d125b> SUSE LINUX Products GmbH | Maxfeldstr. 5 | 90409 Nürnberg | Germany "" |
|
From: Amir G. <ami...@gm...> - 2012-05-08 08:31:29
|
Cool. Thanks! Sent from my private persona, enabled by Cellrox On May 8, 2012 11:22 AM, "Kim Hagen" <kh...@mu...> wrote: > Hi Amir, > > I think the install works.. > the version is: > ./bin/next3 version > snapshot-version = next3 snapshot v1.0.13-8 (2-Aug-2011) > (this was done by adding ./bin/next3 version in the make test section of > the makefile just before rmmod) > > this is the output of the "make test" > grep next3 /proc/modules || /sbin/insmod next3/next3.ko > (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 ) > Filesystem UUID: 6fab4b7e-464d-463e-bc9c-854d0ca1ab19 > mkdir -p test > mount -t next3 | grep test || mount -t next3 test.img -o loop test > ./bin/next3 tests > snapshot /usr/src/next3-1.0.13/test@1 was unmounted > . > snapshot /usr/src/next3-1.0.13/test@1 is deleted > . > snapshot /usr/src/next3-1.0.13/test@2 was unmounted > . > snapshot /usr/src/next3-1.0.13/test@2 is deleted > . > snapshot /usr/src/next3-1.0.13/test@3 was unmounted > . > snapshot /usr/src/next3-1.0.13/test@3 is deleted > . > snapshot /usr/src/next3-1.0.13/test@4 was unmounted > . > snapshot /usr/src/next3-1.0.13/test@4 is deleted > . > snapshot /usr/src/next3-1.0.13/test@1 was unmounted > . > snapshot /usr/src/next3-1.0.13/test@1 is deleted > . > snapshot /usr/src/next3-1.0.13/test@1 was removed > . > snapshot /usr/src/next3-1.0.13/test@2 was unmounted > . > snapshot /usr/src/next3-1.0.13/test@2 is deleted > . > snapshot /usr/src/next3-1.0.13/test@2 was removed > . > snapshot /usr/src/next3-1.0.13/test@3 was unmounted > . > snapshot /usr/src/next3-1.0.13/test@3 is deleted > . > snapshot /usr/src/next3-1.0.13/test@3 was removed > . > snapshot /usr/src/next3-1.0.13/test@4 was unmounted > . > snapshot /usr/src/next3-1.0.13/test@4 is deleted > . > snapshot /usr/src/next3-1.0.13/test@4 was removed > . > > Running snapshot test 1: > ------------------------ > 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 > Files in file system: > A/a.txt:aligator > B/b.txt:bizon > C/c.txt:camel > 1M.1: OK > . > snapshot /usr/src/next3-1.0.13/test@1 was created > . > Create test: > ------------ > Creating d.txt > Creating e.txt > . > Files in file system: > A/a.txt:aligator > B/b.txt:bizon > C/c.txt:camel > D/d.txt:dodo > E/e.txt:emu > 1M.1: OK > . > snapshot /usr/src/next3-1.0.13/test@1 is mounted > . > Files in snapshot 1: > A/a.txt:aligator > B/b.txt:bizon > C/c.txt:camel > 1M.1: OK > . > /dev/loop1 /usr/src/next3-1.0.13/test@1 ext2 ro,relatime 0 0 > snapshot /usr/src/next3-1.0.13/test@1 was unmounted > . > Mounted next3 filesystem and snapshots: > Filesystem Size Used Avail Use% Mounted on > /dev/loop0 4.0G 138M 3.6G 4% /usr/src/next3-1.0.13/test > . > Snapshots list: > id inode attributes disk-usage mtime filename > --------------------------------------------- > 6 106498 S-a----- 92K May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/1 > . > > Running snapshot test 2: > ------------------------ > Appending 1M zeros to 1M.1 with direct I/O > 1+0 records in > 1+0 records out > Writing 1M random data to 2 files > Files in file system: > A/a.txt:aligator > B/b.txt:bizon > C/c.txt:camel > D/d.txt:dodo > E/e.txt:emu > 1M.1: OK > 1M.2: OK > . > snapshot /usr/src/next3-1.0.13/test@2 was created > . > Write test: > ----------- > Writing b.txt (append) > Writing c.txt (truncate) > . > Files in file system: > A/a.txt:aligator > B/b.txt:bizon > B/b.txt:barracuda > C/c.txt:crocodile > D/d.txt:dodo > E/e.txt:emu > 1M.1: OK > 1M.2: OK > . > snapshot /usr/src/next3-1.0.13/test@2 is mounted > . > Files in snapshot 2: > A/a.txt:aligator > B/b.txt:bizon > C/c.txt:camel > D/d.txt:dodo > E/e.txt:emu > 1M.1: OK > 1M.2: OK > . > /dev/loop1 /usr/src/next3-1.0.13/test@2 ext2 ro,relatime 0 0 > snapshot /usr/src/next3-1.0.13/test@2 was unmounted > . > Mounted next3 filesystem and snapshots: > Filesystem Size Used Avail Use% Mounted on > /dev/loop0 4.0G 140M 3.6G 4% /usr/src/next3-1.0.13/test > . > Snapshots list: > id inode attributes disk-usage mtime filename > --------------------------------------------- > 7 106499 S-a----- 84K May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/2 > 6 106498 S------- 1.2M May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/1 > . > > Running snapshot test 3: > ------------------------ > Appending 1M zeros to 1M.1 with direct I/O > 1+0 records in > 1+0 records out > Writing 1M random data to 3 files > Files in file system: > A/a.txt:aligator > B/b.txt:bizon > B/b.txt:barracuda > C/c.txt:crocodile > D/d.txt:dodo > E/e.txt:emu > 1M.1: OK > 1M.2: OK > 1M.3: OK > . > snapshot /usr/src/next3-1.0.13/test@3 was created > . > Remove test: > ------------ > Truncating c.txt (to size 4) > Removing d.txt > . > Files in file system: > A/a.txt:aligator > B/b.txt:bizon > B/b.txt:barracuda > C/c.txt:croc > E/e.txt:emu > 1M.1: OK > 1M.2: OK > 1M.3: OK > . > snapshot /usr/src/next3-1.0.13/test@3 is mounted > . > Files in snapshot 3: > A/a.txt:aligator > B/b.txt:bizon > B/b.txt:barracuda > C/c.txt:crocodile > D/d.txt:dodo > E/e.txt:emu > 1M.1: OK > 1M.2: OK > 1M.3: OK > . > /dev/loop1 /usr/src/next3-1.0.13/test@3 ext2 ro,relatime 0 0 > snapshot /usr/src/next3-1.0.13/test@3 was unmounted > . > Mounted next3 filesystem and snapshots: > Filesystem Size Used Avail Use% Mounted on > /dev/loop0 4.0G 143M 3.6G 4% /usr/src/next3-1.0.13/test > . > Snapshots list: > id inode attributes disk-usage mtime filename > --------------------------------------------- > 8 106500 S-a----- 96K May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/3 > 7 106499 S------- 2.2M May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/2 > 6 106498 S------- 1.2M May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/1 > . > > Running snapshot test 4: > ------------------------ > Appending 1M zeros to 1M.1 with direct I/O > 1+0 records in > 1+0 records out > Writing 1M random data to 4 files > Files in file system: > A/a.txt:aligator > B/b.txt:bizon > B/b.txt:barracuda > C/c.txt:croc > E/e.txt:emu > 1M.1: OK > 1M.2: OK > 1M.3: OK > 1M.4: OK > . > snapshot /usr/src/next3-1.0.13/test@4 was created > . > Restore test: > ------------- > Restoring from snapshot 1 > snapshot /usr/src/next3-1.0.13/test@1 is mounted > . > /dev/loop1 /usr/src/next3-1.0.13/test@1 ext2 ro,relatime 0 0 > snapshot /usr/src/next3-1.0.13/test@1 was unmounted > . > . > Files in file system: > A/a.txt:aligator > B/b.txt:bizon > C/c.txt:camel > 1M.1: OK > 1M.2: OK > 1M.3: OK > 1M.4: OK > . > snapshot /usr/src/next3-1.0.13/test@4 is mounted > . > Files in snapshot 4: > A/a.txt:aligator > B/b.txt:bizon > B/b.txt:barracuda > C/c.txt:croc > E/e.txt:emu > 1M.1: OK > 1M.2: OK > 1M.3: OK > 1M.4: OK > . > /dev/loop1 /usr/src/next3-1.0.13/test@4 ext2 ro,relatime 0 0 > snapshot /usr/src/next3-1.0.13/test@4 was unmounted > . > Mounted next3 filesystem and snapshots: > Filesystem Size Used Avail Use% Mounted on > /dev/loop0 4.0G 148M 3.6G 4% /usr/src/next3-1.0.13/test > . > Snapshots list: > id inode attributes disk-usage mtime filename > --------------------------------------------- > 9 106501 S-a----- 260K May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/4 > 8 106500 S------- 3.2M May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/3 > 7 106499 S------- 2.2M May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/2 > 6 106498 S------- 1.2M May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/1 > . > Files in file system: > A/a.txt:aligator > B/b.txt:bizon > C/c.txt:camel > 1M.1: OK > 1M.2: OK > 1M.3: OK > 1M.4: OK > . > snapshot /usr/src/next3-1.0.13/test@1 is mounted > . > Files in snapshot 1: > A/a.txt:aligator > B/b.txt:bizon > C/c.txt:camel > 1M.1: OK > . > /dev/loop1 /usr/src/next3-1.0.13/test@1 ext2 ro,relatime 0 0 > snapshot /usr/src/next3-1.0.13/test@1 was unmounted > . > snapshot /usr/src/next3-1.0.13/test@2 is mounted > . > Files in snapshot 2: > A/a.txt:aligator > B/b.txt:bizon > C/c.txt:camel > D/d.txt:dodo > E/e.txt:emu > 1M.1: OK > 1M.2: OK > . > /dev/loop1 /usr/src/next3-1.0.13/test@2 ext2 ro,relatime 0 0 > snapshot /usr/src/next3-1.0.13/test@2 was unmounted > . > snapshot /usr/src/next3-1.0.13/test@3 is mounted > . > Files in snapshot 3: > A/a.txt:aligator > B/b.txt:bizon > B/b.txt:barracuda > C/c.txt:crocodile > D/d.txt:dodo > E/e.txt:emu > 1M.1: OK > 1M.2: OK > 1M.3: OK > . > /dev/loop1 /usr/src/next3-1.0.13/test@3 ext2 ro,relatime 0 0 > snapshot /usr/src/next3-1.0.13/test@3 was unmounted > . > snapshot /usr/src/next3-1.0.13/test@4 is mounted > . > Files in snapshot 4: > A/a.txt:aligator > B/b.txt:bizon > B/b.txt:barracuda > C/c.txt:croc > E/e.txt:emu > 1M.1: OK > 1M.2: OK > 1M.3: OK > 1M.4: OK > . > /dev/loop1 /usr/src/next3-1.0.13/test@4 ext2 ro,relatime 0 0 > snapshot /usr/src/next3-1.0.13/test@4 was unmounted > . > Fscking snapshot /usr/src/next3-1.0.13/test@1... > snapshot /usr/src/next3-1.0.13/test@1 is healthy > . > Fscking snapshot /usr/src/next3-1.0.13/test@2... > snapshot /usr/src/next3-1.0.13/test@2 is healthy > . > Fscking snapshot /usr/src/next3-1.0.13/test@3... > snapshot /usr/src/next3-1.0.13/test@3 is healthy > . > Fscking snapshot /usr/src/next3-1.0.13/test@4... > snapshot /usr/src/next3-1.0.13/test@4 is healthy > . > ./bin/next3 umount > snapshot /usr/src/next3-1.0.13/test@1 was unmounted > . > snapshot /usr/src/next3-1.0.13/test@2 was unmounted > . > snapshot /usr/src/next3-1.0.13/test@3 was unmounted > . > snapshot /usr/src/next3-1.0.13/test@4 was unmounted > . > next3 filesystem was unmounted > . > /sbin/rmmod next3 > > > Kind regards, > > Kim > > > > From: Amir Goldstein <ami...@gm...> > To: Kim Hagen <kh...@mu...>, > Cc: next3 <nex...@li...> > Date: 05/08/2012 07:51 AM > Subject: Re: [Next3-users] Kernel bug.. > ------------------------------ > > > > Hi Kim, > > I uploaded the patch to *next3.sf.net* <http://next3.sf.net/>. > Can you please verify that the install works for you: > cd next3-1.0.13 > make distclean > make module > > I don't have a ready setup with kernel <= 2.6.35 to test it. > Thanks, > Amir. > > On Sat, May 5, 2012 at 5:22 PM, Kim Hagen <*kh...@mu...*<kh...@mu...>> > wrote: > Hi Amir, > > The patch is attached. > > Kind regards, > > Kim > > > -----Amir Goldstein <*ami...@gm...* <ami...@gm...>> wrote: > ----- > To: Kim Hagen <*kh...@mu...*<kh...@mu...> > > > From: Amir Goldstein <*ami...@gm...* <ami...@gm...>> > Date: 05/05/2012 02:34PM > Cc: next3 <*nex...@li...*<nex...@li...> > > > > Subject: Re: [Next3-users] Kernel bug.. > > Hi Kim, > > Glad to hear. > CC-ing next3-devel, where we should have has this discussion. > If you send me the generated patch I will upload it to the *next3.sf.net*<http://next3.sf.net/>web site. > > Thanks, > Amir. > > On Sat, May 5, 2012 at 12:54 PM, Kim Hagen <*kh...@mu...*<kh...@mu...>> > wrote: > Hi Amir, > > I could not get the clone of the stable branch so i downloaded each file > individually > in the fs next3 folder :) > > The build was without any problems, the module version now indeed is > v1.0.13-8, > and is stable now for a few days, no error messages in dmesg and logs. > > Thank you very much for your help. > > Kind regards, > > Kim Hagen > > -----Amir Goldstein <*ami...@gm...* <ami...@gm...>> wrote: > ----- > To: Kim Hagen <*kh...@mu...*<kh...@mu...> > > > From: Amir Goldstein <*ami...@gm...* <ami...@gm...>> > Date: 05/02/2012 04:03PM > Cc: *nex...@li...*<nex...@li...> > > Subject: Re: [Next3-users] Kernel bug.. > > 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...*<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*<http://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...*<kh...@mu...> > > > To: Amir Goldstein <*ami...@gm...* <ami...@gm...>>, > Cc: *nex...@li...*<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...* <ami...@gm...>> > To: Kim Hagen <*kh...@mu...*<kh...@mu...>>, > > Cc: *nex...@li...*<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: > > > > 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-08 08:22:28
|
Hi Amir,
I think the install works..
the version is:
./bin/next3 version
snapshot-version = next3 snapshot v1.0.13-8 (2-Aug-2011)
(this was done by adding ./bin/next3 version in the make test section of
the makefile just before rmmod)
this is the output of the "make test"
grep next3 /proc/modules || /sbin/insmod next3/next3.ko
(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 )
Filesystem UUID: 6fab4b7e-464d-463e-bc9c-854d0ca1ab19
mkdir -p test
mount -t next3 | grep test || mount -t next3 test.img -o loop test
./bin/next3 tests
snapshot /usr/src/next3-1.0.13/test@1 was unmounted
.
snapshot /usr/src/next3-1.0.13/test@1 is deleted
.
snapshot /usr/src/next3-1.0.13/test@2 was unmounted
.
snapshot /usr/src/next3-1.0.13/test@2 is deleted
.
snapshot /usr/src/next3-1.0.13/test@3 was unmounted
.
snapshot /usr/src/next3-1.0.13/test@3 is deleted
.
snapshot /usr/src/next3-1.0.13/test@4 was unmounted
.
snapshot /usr/src/next3-1.0.13/test@4 is deleted
.
snapshot /usr/src/next3-1.0.13/test@1 was unmounted
.
snapshot /usr/src/next3-1.0.13/test@1 is deleted
.
snapshot /usr/src/next3-1.0.13/test@1 was removed
.
snapshot /usr/src/next3-1.0.13/test@2 was unmounted
.
snapshot /usr/src/next3-1.0.13/test@2 is deleted
.
snapshot /usr/src/next3-1.0.13/test@2 was removed
.
snapshot /usr/src/next3-1.0.13/test@3 was unmounted
.
snapshot /usr/src/next3-1.0.13/test@3 is deleted
.
snapshot /usr/src/next3-1.0.13/test@3 was removed
.
snapshot /usr/src/next3-1.0.13/test@4 was unmounted
.
snapshot /usr/src/next3-1.0.13/test@4 is deleted
.
snapshot /usr/src/next3-1.0.13/test@4 was removed
.
Running snapshot test 1:
------------------------
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
Files in file system:
A/a.txt:aligator
B/b.txt:bizon
C/c.txt:camel
1M.1: OK
.
snapshot /usr/src/next3-1.0.13/test@1 was created
.
Create test:
------------
Creating d.txt
Creating e.txt
.
Files in file system:
A/a.txt:aligator
B/b.txt:bizon
C/c.txt:camel
D/d.txt:dodo
E/e.txt:emu
1M.1: OK
.
snapshot /usr/src/next3-1.0.13/test@1 is mounted
.
Files in snapshot 1:
A/a.txt:aligator
B/b.txt:bizon
C/c.txt:camel
1M.1: OK
.
/dev/loop1 /usr/src/next3-1.0.13/test@1 ext2 ro,relatime 0 0
snapshot /usr/src/next3-1.0.13/test@1 was unmounted
.
Mounted next3 filesystem and snapshots:
Filesystem Size Used Avail Use% Mounted on
/dev/loop0 4.0G 138M 3.6G 4% /usr/src/next3-1.0.13/test
.
Snapshots list:
id inode attributes disk-usage mtime filename
---------------------------------------------
6 106498 S-a----- 92K May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/1
.
Running snapshot test 2:
------------------------
Appending 1M zeros to 1M.1 with direct I/O
1+0 records in
1+0 records out
Writing 1M random data to 2 files
Files in file system:
A/a.txt:aligator
B/b.txt:bizon
C/c.txt:camel
D/d.txt:dodo
E/e.txt:emu
1M.1: OK
1M.2: OK
.
snapshot /usr/src/next3-1.0.13/test@2 was created
.
Write test:
-----------
Writing b.txt (append)
Writing c.txt (truncate)
.
Files in file system:
A/a.txt:aligator
B/b.txt:bizon
B/b.txt:barracuda
C/c.txt:crocodile
D/d.txt:dodo
E/e.txt:emu
1M.1: OK
1M.2: OK
.
snapshot /usr/src/next3-1.0.13/test@2 is mounted
.
Files in snapshot 2:
A/a.txt:aligator
B/b.txt:bizon
C/c.txt:camel
D/d.txt:dodo
E/e.txt:emu
1M.1: OK
1M.2: OK
.
/dev/loop1 /usr/src/next3-1.0.13/test@2 ext2 ro,relatime 0 0
snapshot /usr/src/next3-1.0.13/test@2 was unmounted
.
Mounted next3 filesystem and snapshots:
Filesystem Size Used Avail Use% Mounted on
/dev/loop0 4.0G 140M 3.6G 4% /usr/src/next3-1.0.13/test
.
Snapshots list:
id inode attributes disk-usage mtime filename
---------------------------------------------
7 106499 S-a----- 84K May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/2
6 106498 S------- 1.2M May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/1
.
Running snapshot test 3:
------------------------
Appending 1M zeros to 1M.1 with direct I/O
1+0 records in
1+0 records out
Writing 1M random data to 3 files
Files in file system:
A/a.txt:aligator
B/b.txt:bizon
B/b.txt:barracuda
C/c.txt:crocodile
D/d.txt:dodo
E/e.txt:emu
1M.1: OK
1M.2: OK
1M.3: OK
.
snapshot /usr/src/next3-1.0.13/test@3 was created
.
Remove test:
------------
Truncating c.txt (to size 4)
Removing d.txt
.
Files in file system:
A/a.txt:aligator
B/b.txt:bizon
B/b.txt:barracuda
C/c.txt:croc
E/e.txt:emu
1M.1: OK
1M.2: OK
1M.3: OK
.
snapshot /usr/src/next3-1.0.13/test@3 is mounted
.
Files in snapshot 3:
A/a.txt:aligator
B/b.txt:bizon
B/b.txt:barracuda
C/c.txt:crocodile
D/d.txt:dodo
E/e.txt:emu
1M.1: OK
1M.2: OK
1M.3: OK
.
/dev/loop1 /usr/src/next3-1.0.13/test@3 ext2 ro,relatime 0 0
snapshot /usr/src/next3-1.0.13/test@3 was unmounted
.
Mounted next3 filesystem and snapshots:
Filesystem Size Used Avail Use% Mounted on
/dev/loop0 4.0G 143M 3.6G 4% /usr/src/next3-1.0.13/test
.
Snapshots list:
id inode attributes disk-usage mtime filename
---------------------------------------------
8 106500 S-a----- 96K May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/3
7 106499 S------- 2.2M May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/2
6 106498 S------- 1.2M May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/1
.
Running snapshot test 4:
------------------------
Appending 1M zeros to 1M.1 with direct I/O
1+0 records in
1+0 records out
Writing 1M random data to 4 files
Files in file system:
A/a.txt:aligator
B/b.txt:bizon
B/b.txt:barracuda
C/c.txt:croc
E/e.txt:emu
1M.1: OK
1M.2: OK
1M.3: OK
1M.4: OK
.
snapshot /usr/src/next3-1.0.13/test@4 was created
.
Restore test:
-------------
Restoring from snapshot 1
snapshot /usr/src/next3-1.0.13/test@1 is mounted
.
/dev/loop1 /usr/src/next3-1.0.13/test@1 ext2 ro,relatime 0 0
snapshot /usr/src/next3-1.0.13/test@1 was unmounted
.
.
Files in file system:
A/a.txt:aligator
B/b.txt:bizon
C/c.txt:camel
1M.1: OK
1M.2: OK
1M.3: OK
1M.4: OK
.
snapshot /usr/src/next3-1.0.13/test@4 is mounted
.
Files in snapshot 4:
A/a.txt:aligator
B/b.txt:bizon
B/b.txt:barracuda
C/c.txt:croc
E/e.txt:emu
1M.1: OK
1M.2: OK
1M.3: OK
1M.4: OK
.
/dev/loop1 /usr/src/next3-1.0.13/test@4 ext2 ro,relatime 0 0
snapshot /usr/src/next3-1.0.13/test@4 was unmounted
.
Mounted next3 filesystem and snapshots:
Filesystem Size Used Avail Use% Mounted on
/dev/loop0 4.0G 148M 3.6G 4% /usr/src/next3-1.0.13/test
.
Snapshots list:
id inode attributes disk-usage mtime filename
---------------------------------------------
9 106501 S-a----- 260K May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/4
8 106500 S------- 3.2M May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/3
7 106499 S------- 2.2M May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/2
6 106498 S------- 1.2M May 8 10:17 /usr/src/next3-1.0.13/test/.snapshots/1
.
Files in file system:
A/a.txt:aligator
B/b.txt:bizon
C/c.txt:camel
1M.1: OK
1M.2: OK
1M.3: OK
1M.4: OK
.
snapshot /usr/src/next3-1.0.13/test@1 is mounted
.
Files in snapshot 1:
A/a.txt:aligator
B/b.txt:bizon
C/c.txt:camel
1M.1: OK
.
/dev/loop1 /usr/src/next3-1.0.13/test@1 ext2 ro,relatime 0 0
snapshot /usr/src/next3-1.0.13/test@1 was unmounted
.
snapshot /usr/src/next3-1.0.13/test@2 is mounted
.
Files in snapshot 2:
A/a.txt:aligator
B/b.txt:bizon
C/c.txt:camel
D/d.txt:dodo
E/e.txt:emu
1M.1: OK
1M.2: OK
.
/dev/loop1 /usr/src/next3-1.0.13/test@2 ext2 ro,relatime 0 0
snapshot /usr/src/next3-1.0.13/test@2 was unmounted
.
snapshot /usr/src/next3-1.0.13/test@3 is mounted
.
Files in snapshot 3:
A/a.txt:aligator
B/b.txt:bizon
B/b.txt:barracuda
C/c.txt:crocodile
D/d.txt:dodo
E/e.txt:emu
1M.1: OK
1M.2: OK
1M.3: OK
.
/dev/loop1 /usr/src/next3-1.0.13/test@3 ext2 ro,relatime 0 0
snapshot /usr/src/next3-1.0.13/test@3 was unmounted
.
snapshot /usr/src/next3-1.0.13/test@4 is mounted
.
Files in snapshot 4:
A/a.txt:aligator
B/b.txt:bizon
B/b.txt:barracuda
C/c.txt:croc
E/e.txt:emu
1M.1: OK
1M.2: OK
1M.3: OK
1M.4: OK
.
/dev/loop1 /usr/src/next3-1.0.13/test@4 ext2 ro,relatime 0 0
snapshot /usr/src/next3-1.0.13/test@4 was unmounted
.
Fscking snapshot /usr/src/next3-1.0.13/test@1...
snapshot /usr/src/next3-1.0.13/test@1 is healthy
.
Fscking snapshot /usr/src/next3-1.0.13/test@2...
snapshot /usr/src/next3-1.0.13/test@2 is healthy
.
Fscking snapshot /usr/src/next3-1.0.13/test@3...
snapshot /usr/src/next3-1.0.13/test@3 is healthy
.
Fscking snapshot /usr/src/next3-1.0.13/test@4...
snapshot /usr/src/next3-1.0.13/test@4 is healthy
.
./bin/next3 umount
snapshot /usr/src/next3-1.0.13/test@1 was unmounted
.
snapshot /usr/src/next3-1.0.13/test@2 was unmounted
.
snapshot /usr/src/next3-1.0.13/test@3 was unmounted
.
snapshot /usr/src/next3-1.0.13/test@4 was unmounted
.
next3 filesystem was unmounted
.
/sbin/rmmod next3
Kind regards,
Kim
From: Amir Goldstein <ami...@gm...>
To: Kim Hagen <kh...@mu...>,
Cc: next3 <nex...@li...>
Date: 05/08/2012 07:51 AM
Subject: Re: [Next3-users] Kernel bug..
Hi Kim,
I uploaded the patch to next3.sf.net.
Can you please verify that the install works for you:
cd next3-1.0.13
make distclean
make module
I don't have a ready setup with kernel <= 2.6.35 to test it.
Thanks,
Amir.
On Sat, May 5, 2012 at 5:22 PM, Kim Hagen <kh...@mu...>
wrote:
Hi Amir,
The patch is attached.
Kind regards,
Kim
-----Amir Goldstein <ami...@gm...> wrote: -----
To: Kim Hagen <kh...@mu...>
From: Amir Goldstein <ami...@gm...>
Date: 05/05/2012 02:34PM
Cc: next3 <nex...@li...>
Subject: Re: [Next3-users] Kernel bug..
Hi Kim,
Glad to hear.
CC-ing next3-devel, where we should have has this discussion.
If you send me the generated patch I will upload it to the next3.sf.net
web site.
Thanks,
Amir.
On Sat, May 5, 2012 at 12:54 PM, Kim Hagen <kh...@mu...>
wrote:
Hi Amir,
I could not get the clone of the stable branch so i downloaded each file
individually
in the fs next3 folder :)
The build was without any problems, the module version now indeed is
v1.0.13-8,
and is stable now for a few days, no error messages in dmesg and logs.
Thank you very much for your help.
Kind regards,
Kim Hagen
-----Amir Goldstein <ami...@gm...> wrote: -----
To: Kim Hagen <kh...@mu...>
From: Amir Goldstein <ami...@gm...>
Date: 05/02/2012 04:03PM
Cc: nex...@li...
Subject: Re: [Next3-users] Kernel bug..
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
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:
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-08 05:51:45
|
Hi Kim, I uploaded the patch to next3.sf.net. Can you please verify that the install works for you: cd next3-1.0.13 make distclean make module I don't have a ready setup with kernel <= 2.6.35 to test it. Thanks, Amir. On Sat, May 5, 2012 at 5:22 PM, Kim Hagen <kh...@mu...>wrote: > Hi Amir, > > The patch is attached. > > Kind regards, > > Kim > > > -----Amir Goldstein <ami...@gm...> wrote: ----- > To: Kim Hagen <kh...@mu...> > From: Amir Goldstein <ami...@gm...> > Date: 05/05/2012 02:34PM > Cc: next3 <nex...@li...> > > Subject: Re: [Next3-users] Kernel bug.. > > Hi Kim, > > Glad to hear. > CC-ing next3-devel, where we should have has this discussion. > If you send me the generated patch I will upload it to the next3.sf.netweb site. > > Thanks, > Amir. > > On Sat, May 5, 2012 at 12:54 PM, Kim Hagen <kh...@mu...>wrote: > >> Hi Amir, >> >> I could not get the clone of the stable branch so i downloaded each file >> individually >> in the fs next3 folder :) >> >> The build was without any problems, the module version now indeed is >> v1.0.13-8, >> and is stable now for a few days, no error messages in dmesg and logs. >> >> Thank you very much for your help. >> >> Kind regards, >> >> Kim Hagen >> >> -----Amir Goldstein <ami...@gm...> wrote: ----- >> To: Kim Hagen <kh...@mu...> >> From: Amir Goldstein <ami...@gm...> >> Date: 05/02/2012 04:03PM >> Cc: nex...@li... >> >> Subject: Re: [Next3-users] Kernel bug.. >> >> 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: >>> >>> >>> >>> 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... > 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-05 15:55:06
|
<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2">Hi Amir,<br><br>The patch is attached.<br><br>Kind regards,<br><br>Kim<br><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/05/2012 02:34PM<br>Cc: next3 <nex...@li...><br>Subject: Re: [Next3-users] Kernel bug..<br><br><div dir="ltr">Hi Kim,<div><br></div><div>Glad to hear.</div><div>CC-ing next3-devel, where we should have has this discussion.</div><div>If you send me the generated patch I will upload it to the <a href="http://next3.sf.net" target="_blank">next3.sf.net</a> web site.</div> <div><br></div><div>Thanks,</div><div> Amir.<br><br><div class="gmail_quote">On Sat, May 5, 2012 at 12:54 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="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif">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 <<a href="mailto:ami...@gm..." target="_blank">ami...@gm...</a>> wrote: -----</font><div style="padding-left:5px"> <div style="padding-right:0px;padding-left:5px;border-left:solid black 2px">To: Kim Hagen <<a href="mailto:kh...@mu..." target="_blank">kh...@mu...</a>><br>From: Amir Goldstein <<a href="mailto:ami...@gm..." target="_blank">ami...@gm...</a>><br> Date: 05/02/2012 04:03PM<br>Cc: <a href="mailto:nex...@li..." target="_blank">nex...@li...</a><div><div><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><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><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">"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></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> </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></font></div></div></blockquote></div></div></div></div></div></div></div></font></blockquote></div></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-05 12:34:24
|
Hi Kim, Glad to hear. CC-ing next3-devel, where we should have has this discussion. If you send me the generated patch I will upload it to the next3.sf.net web site. Thanks, Amir. On Sat, May 5, 2012 at 12:54 PM, Kim Hagen <kh...@mu...>wrote: > Hi Amir, > > I could not get the clone of the stable branch so i downloaded each file > individually > in the fs next3 folder :) > > The build was without any problems, the module version now indeed is > v1.0.13-8, > and is stable now for a few days, no error messages in dmesg and logs. > > Thank you very much for your help. > > Kind regards, > > Kim Hagen > > -----Amir Goldstein <ami...@gm...> wrote: ----- > To: Kim Hagen <kh...@mu...> > From: Amir Goldstein <ami...@gm...> > Date: 05/02/2012 04:03PM > Cc: nex...@li... > > Subject: Re: [Next3-users] Kernel bug.. > > 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: >> >> >> >> 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 >> >> >> >> >> >> >> |
|
From: Vicky D. <vic...@ed...> - 2012-03-19 05:25:30
|
please do needful.
--
Thanks n Regards,
Vicky DEEPOOA - _LINUX
Developer_
ENTERPRISE DATA SERVICES | | TEL (+230) 465 1700
--------
Original Message --------
Re: FW: Documentation for Next3
Sat,
17 Mar 2012 10:18:42 +0200
"Amir G."
Vicky DEEPOOA
Hi
Vicky,
Sorry I missed your email. better send these kind of emails to
nex...@li... [1].
More information on Next3 is
available on: http://next3.sourceforge.net/ [2]
https://sourceforge.net/apps/mediawiki/next3/ [3]
The next3 standalone
module is available for build with kernel versions
2.6.31-2.6.35, so it
depends if you upgrade the Debian 5 kernel to one of these versions.
Amir.
________________________________________
From: Vicky DEEPOOA
[vic...@ed... [4]]
Sent: Tuesday, February 21, 2012 12:21 PM
To:
Amir Goldstein
Subject: Documentation for Next3
Hello,
Is there a
technical doc available for implementing next3 on Debian 5 ?
--
Thanks
n Regards,
Vicky DEEPOOA - LINUX Developer
Enterprise Data Services |
www.eds.mu [5] | TEL (+230) 465 1700
Links:
------
[1]
mailto:nex...@li...
[2]
http://next3.sourceforge.net/
[3]
https://sourceforge.net/apps/mediawiki/next3/index.php?title=Main_Page
[4]
mailto:vic...@ed...
[5] http://www.eds.mu
[6] http://www.eds.mu
|
|
From: Amir G. <ami...@gm...> - 2012-02-21 07:49:55
|
Hi all, I just got back from Embedded Linux Conference. Had a nice surprise in the traditional kernel report. Check out June in the kernel report: https://events.linuxfoundation.org/images/stories/pdf/lf_elc12_corbet.pdf I hope that Ext4 snapshots project will awake from its winter slumber and return to the kernel report headlines next year. Google summer of code 2012 has started and if you have any project ideas, you are welcome to post them. Cheers, Amir. |
|
From: Amir G. <ami...@gm...> - 2011-12-09 18:07:44
|
Hi Greg, FYI, Ctera products have had the shadow copy feature from the first days on NEXT3. It is actually not do hard to set this up with samba. It's just a matter of snapshots naming convention (date-time) and of mounting the snapshots at the root of the share. Cheers, Amir. On Fri, Dec 9, 2011 at 7:31 PM, Greg Freemyer <gre...@gm...> wrote: > On Fri, Dec 9, 2011 at 11:06 AM, Lars Müller <lm...@su...> wrote: >> c) We'll make us of this with Samba >> >> And to put more cream on top of it we're working on offering access to >> the btrfs snapshots via Samba to Microsoft Windows users. All a user of >> a Samba share has to do at the end is a right cklick on the folder in a >> Microsoft Explorer window and from the properties window you'll have >> access to the btrfs snapshots like you're able to access native >> Microsoft Shadow Copy snapshots. See >> http://en.wikipedia.org/wiki/Shadow_Copy if you havn't used this before. > > That is beyond cool. In fact it is way beyond cool. > > I've cc'ed the ext3/ext4 snapshots mailinglist. They may have some > questions for you about this. > > Greg > > ------------------------------------------------------------------------------ > Cloud Services Checklist: Pricing and Packaging Optimization > This white paper is intended to serve as a reference, checklist and point of > discussion for anyone considering optimizing the pricing and packaging model > of a cloud services business. Read Now! > http://www.accelacomm.com/jaw/sfnl/114/51491232/ > _______________________________________________ > Next3-devel mailing list > Nex...@li... > https://lists.sourceforge.net/lists/listinfo/next3-devel |
|
From: Greg F. <gre...@gm...> - 2011-12-09 17:32:05
|
On Fri, Dec 9, 2011 at 11:06 AM, Lars Müller <lm...@su...> wrote: > c) We'll make us of this with Samba > > And to put more cream on top of it we're working on offering access to > the btrfs snapshots via Samba to Microsoft Windows users. All a user of > a Samba share has to do at the end is a right cklick on the folder in a > Microsoft Explorer window and from the properties window you'll have > access to the btrfs snapshots like you're able to access native > Microsoft Shadow Copy snapshots. See > http://en.wikipedia.org/wiki/Shadow_Copy if you havn't used this before. That is beyond cool. In fact it is way beyond cool. I've cc'ed the ext3/ext4 snapshots mailinglist. They may have some questions for you about this. Greg |
|
From: Amir G. <ami...@gm...> - 2011-11-11 23:58:45
|
Hi Sergey, I was wondering if you could help out in testing the latest 3.1 kernel module, as you now have it running on Fedora-16. Can you please try a full run of xfstest (latest official repo) on an ext4 fs with snapshots. There are some reports below from Greg about failing tests and there is the old test 070 bug which does not seem to happen for everyone. I also wanted to ask for a favor. I can no longer use the test server I was using until recently, so I was wondering if it would be possible for you to provide ssh access to a test server, for myself and Yongqiang, so we can run regression tests on it. Yongqiang doesn't get the test 070 bug on his system, so if we see that bug on the test server it could be very helpful for debugging the problem. Thanks, Amir. On Thu, Nov 3, 2011 at 5:06 AM, Yongqiang Yang <xia...@gm...> wrote: > On Thu, Nov 3, 2011 at 3:22 AM, Amir Goldstein <ami...@gm...> wrote: >> On Wed, Nov 2, 2011 at 9:00 PM, Greg Freemyer <gre...@gm...> wrote: >>> On Wed, Nov 2, 2011 at 2:54 PM, Amir Goldstein <ami...@gm...> wrote: >>>> On Wed, Nov 2, 2011 at 5:17 PM, Greg Freemyer <gre...@gm...> wrote: >>>>> Amir, >>>>> >>>>> I am now running kernel 3.1.0 with the ext4dev-kmp compiled from home:next4. >>>> >>>> and this is the same kernel that worked fine with the kmp from filesystems repo? >>>> >>> >>> No, that was 3.1.0-RC9 >>> >>> So this is both a new kernel and newly compiled KMP. >> >> So maybe just to be sure that we didn't break anything with the merge, >> you can try to install the KMP from fs repo. >> I think it should run with kernel 3.1... >> >>> >>>>> >>>>> I tried xfstests "./check -g auto" from Aditya's git repo. >>>>> >>>>> It failed on both test 113 and 255. That is on the first pass, so no >>>>> snapshots were active. I "assume" that the official ext4 in 3.1.0 doesn't >>>>> fail, but I haven't tested it. >>>> >>>> can you send the detailed error reports of those tests. >>> >>> I don't find a lot of output for 113, but here's what I have: >>> >>>> cat 113.out.bad >>> QA output created by 113 >>> brevity is wit... >>> >>> ----------------------------------------------- >>> aio-stress.1 : -s 120m >>> ----------------------------------------------- >>> ./113: line 47: 32471 Segmentation fault $here/ltp/aio-stress >> >> SEGFAULT usually means some IO error, so you should look at dmesg >> for errors from ext4dev fs. >> >>> $_param $AIOSTRESS_AVOID -I $_count $_files >> $tmp.out 2>&1 >>> aio-stress (count=1000) returned 0 >>> file size 120MB, record size 64KB, depth 64, ios per iteration 8 >>> max io_submit 8, buffer alignment set to 4KB >>> threads 1 files 1 contexts 1 context offset 2MB verification off >>> >>> >>> >>> And for 255 it's >>> >> >> I don't know much about this test, but I reckon Yongqiang knows a lot about it. > There are falloc and punch hole tests in 255. It should has nothing > to do with snapshot. >> >> in general I don't like the fact that xfstest is not uptodate. >> there have been some bugfixes in xfstest, especially in those 25? tests. > Yeah. xfstests has a lot fixes in recent release, especially in fsx. >> >> Aditya, could you rebase/merge your xfstests repo to recent xfstests. >> This probably means changing the test number again... > > We'd better update to latest xfstests. Three days ago, I updated my > xfstests tree to latest one and found a bug in ext4 related to punch > hole and the patch has been merged to upstream by Tytso and will > appear in 3.2 releases. I am not sure if it is related to this > error. > > Yongqiang. >> >> Thanks, >> Amir. >> >> >> >> >>>> cat 255.out.bad >>> QA output created by 255 >>> 1. into a hole >>> daa100df6e6711906b61c9ab5aa16032 >>> 2. into allocated space >>> 0: [0..7]: extent >>> 1: [8..23]: hole >>> 2: [24..39]: extent >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 3. into unwritten space >>> daa100df6e6711906b61c9ab5aa16032 >>> 4. hole -> data >>> 0: [0..23]: hole >>> 1: [24..31]: extent >>> 2: [32..39]: hole >>> cc63069677939f69a6e8f68cae6a6dac >>> 5. hole -> unwritten >>> daa100df6e6711906b61c9ab5aa16032 >>> 6. data -> hole >>> 0: [0..7]: extent >>> 1: [8..39]: hole >>> 1b3779878366498b28c702ef88c4a773 >>> 7. data -> unwritten >>> 0: [0..7]: extent >>> 1: [8..23]: hole >>> 2: [24..31]: extent >>> 3: [32..39]: hole >>> 1b3779878366498b28c702ef88c4a773 >>> 8. unwritten -> hole >>> daa100df6e6711906b61c9ab5aa16032 >>> 9. unwritten -> data >>> 0: [0..7]: extent >>> 1: [8..23]: hole >>> 2: [24..31]: extent >>> 3: [32..39]: hole >>> cc63069677939f69a6e8f68cae6a6dac >>> 10. hole -> data -> hole >>> daa100df6e6711906b61c9ab5aa16032 >>> 11. data -> hole -> data >>> 0: [0..7]: extent >>> 1: [8..31]: hole >>> 2: [32..39]: extent >>> f6aeca13ec49e5b266cd1c913cd726e3 >>> 12. unwritten -> data -> unwritten >>> 0: [0..7]: extent >>> 1: [8..31]: hole >>> 2: [32..39]: extent >>> daa100df6e6711906b61c9ab5aa16032 >>> 13. data -> unwritten -> data >>> 0: [0..7]: extent >>> 1: [8..31]: hole >>> 2: [32..39]: extent >>> f6aeca13ec49e5b266cd1c913cd726e3 >>> 14. data -> hole @ EOF >>> 0: [0..23]: extent >>> 1: [24..39]: hole >>> e1f024eedd27ea6b1c3e9b841c850404 >>> 15. data -> hole @ 0 >>> 0: [0..15]: hole >>> 1: [16..39]: extent >>> eecb7aa303d121835de05028751d301c >>> 16. data -> cache cold ->hole >>> 0: [0..15]: hole >>> 1: [16..39]: extent >>> eecb7aa303d121835de05028751d301c >>> 17. data -> hole in single block file >>> 0: [0..7]: extent >>> 13535fd4d496bf0b74bb2335aa4d1b31 >>> 1. into a hole >>> daa100df6e6711906b61c9ab5aa16032 >>> 2. into allocated space >>> 0: [0..7]: extent >>> 1: [8..23]: hole >>> 2: [24..39]: extent >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 3. into unwritten space >>> daa100df6e6711906b61c9ab5aa16032 >>> 4. hole -> data >>> 0: [0..23]: hole >>> 1: [24..31]: extent >>> 2: [32..39]: hole >>> cc63069677939f69a6e8f68cae6a6dac >>> 5. hole -> unwritten >>> daa100df6e6711906b61c9ab5aa16032 >>> 6. data -> hole >>> 0: [0..7]: extent >>> 1: [8..39]: hole >>> 1b3779878366498b28c702ef88c4a773 >>> 7. data -> unwritten >>> 0: [0..7]: extent >>> 1: [8..23]: hole >>> 2: [24..31]: extent >>> 3: [32..39]: hole >>> 1b3779878366498b28c702ef88c4a773 >>> 8. unwritten -> hole >>> daa100df6e6711906b61c9ab5aa16032 >>> 9. unwritten -> data >>> 0: [0..7]: extent >>> 1: [8..23]: hole >>> 2: [24..31]: extent >>> 3: [32..39]: hole >>> cc63069677939f69a6e8f68cae6a6dac >>> 10. hole -> data -> hole >>> daa100df6e6711906b61c9ab5aa16032 >>> 11. data -> hole -> data >>> 0: [0..7]: extent >>> 1: [8..31]: hole >>> 2: [32..39]: extent >>> f6aeca13ec49e5b266cd1c913cd726e3 >>> 12. unwritten -> data -> unwritten >>> 0: [0..7]: extent >>> 1: [8..31]: hole >>> 2: [32..39]: extent >>> daa100df6e6711906b61c9ab5aa16032 >>> 13. data -> unwritten -> data >>> 0: [0..7]: extent >>> 1: [8..31]: hole >>> 2: [32..39]: extent >>> f6aeca13ec49e5b266cd1c913cd726e3 >>> 14. data -> hole @ EOF >>> 0: [0..23]: extent >>> 1: [24..39]: hole >>> e1f024eedd27ea6b1c3e9b841c850404 >>> 15. data -> hole @ 0 >>> 0: [0..15]: hole >>> 1: [16..39]: extent >>> eecb7aa303d121835de05028751d301c >>> 16. data -> cache cold ->hole >>> 0: [0..15]: hole >>> 1: [16..39]: extent >>> eecb7aa303d121835de05028751d301c >>> 17. data -> hole in single block file >>> 0: [0..7]: extent >>> 13535fd4d496bf0b74bb2335aa4d1b31 >>> 1. into a hole >>> 5a58e46082be047d0f13bee7974015b9 >>> 2. into allocated space >>> 0: [0..7]: extent >>> 1: [8..23]: hole >>> 2: [24..39]: extent >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 3. into unwritten space >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 4. hole -> data >>> 0: [0..7]: extent >>> 1: [8..23]: hole >>> 2: [24..39]: extent >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 5. hole -> unwritten >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 6. data -> hole >>> 0: [0..7]: extent >>> 1: [8..23]: hole >>> 2: [24..39]: extent >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 7. data -> unwritten >>> 0: [0..7]: extent >>> 1: [8..23]: hole >>> 2: [24..39]: extent >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 8. unwritten -> hole >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 9. unwritten -> data >>> 0: [0..7]: extent >>> 1: [8..23]: hole >>> 2: [24..39]: extent >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 10. hole -> data -> hole >>> 0: [0..7]: extent >>> 1: [8..31]: hole >>> 2: [32..39]: extent >>> f6aeca13ec49e5b266cd1c913cd726e3 >>> 11. data -> hole -> data >>> 0: [0..7]: extent >>> 1: [8..31]: hole >>> 2: [32..39]: extent >>> f6aeca13ec49e5b266cd1c913cd726e3 >>> 12. unwritten -> data -> unwritten >>> 0: [0..7]: extent >>> 1: [8..31]: hole >>> 2: [32..39]: extent >>> f6aeca13ec49e5b266cd1c913cd726e3 >>> 13. data -> unwritten -> data >>> 0: [0..7]: extent >>> 1: [8..31]: hole >>> 2: [32..39]: extent >>> f6aeca13ec49e5b266cd1c913cd726e3 >>> 14. data -> hole @ EOF >>> 0: [0..23]: extent >>> 1: [24..39]: hole >>> e1f024eedd27ea6b1c3e9b841c850404 >>> 15. data -> hole @ 0 >>> 0: [0..15]: hole >>> 1: [16..39]: extent >>> eecb7aa303d121835de05028751d301c >>> 16. data -> cache cold ->hole >>> 0: [0..15]: hole >>> 1: [16..39]: extent >>> eecb7aa303d121835de05028751d301c >>> 17. data -> hole in single block file >>> 0: [0..7]: extent >>> 13535fd4d496bf0b74bb2335aa4d1b31 >>> 1. into a hole >>> 5a58e46082be047d0f13bee7974015b9 >>> 2. into allocated space >>> 0: [0..7]: extent >>> 1: [8..23]: hole >>> 2: [24..39]: extent >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 3. into unwritten space >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 4. hole -> data >>> 0: [0..7]: extent >>> 1: [8..23]: hole >>> 2: [24..39]: extent >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 5. hole -> unwritten >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 6. data -> hole >>> 0: [0..7]: extent >>> 1: [8..23]: hole >>> 2: [24..39]: extent >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 7. data -> unwritten >>> 0: [0..7]: extent >>> 1: [8..23]: hole >>> 2: [24..39]: extent >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 8. unwritten -> hole >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 9. unwritten -> data >>> 0: [0..7]: extent >>> 1: [8..23]: hole >>> 2: [24..39]: extent >>> cc58a7417c2d7763adc45b6fcd3fa024 >>> 10. hole -> data -> hole >>> 0: [0..7]: extent >>> 1: [8..31]: hole >>> 2: [32..39]: extent >>> f6aeca13ec49e5b266cd1c913cd726e3 >>> 11. data -> hole -> data >>> 0: [0..7]: extent >>> 1: [8..31]: hole >>> 2: [32..39]: extent >>> f6aeca13ec49e5b266cd1c913cd726e3 >>> 12. unwritten -> data -> unwritten >>> 0: [0..7]: extent >>> 1: [8..31]: hole >>> 2: [32..39]: extent >>> f6aeca13ec49e5b266cd1c913cd726e3 >>> 13. data -> unwritten -> data >>> 0: [0..7]: extent >>> 1: [8..31]: hole >>> 2: [32..39]: extent >>> f6aeca13ec49e5b266cd1c913cd726e3 >>> 14. data -> hole @ EOF >>> 0: [0..23]: extent >>> 1: [24..39]: hole >>> e1f024eedd27ea6b1c3e9b841c850404 >>> 15. data -> hole @ 0 >>> 0: [0..15]: hole >>> 1: [16..39]: extent >>> eecb7aa303d121835de05028751d301c >>> 16. data -> cache cold ->hole >>> 0: [0..15]: hole >>> 1: [16..39]: extent >>> eecb7aa303d121835de05028751d301c >>> 17. data -> hole in single block file >>> 0: [0..7]: extent >>> 13535fd4d496bf0b74bb2335aa4d1b31 >>> >>> >>> >>> Greg >>> >>>> >>>> Thanks, >>>> Amir. >>>> >>>>> >>>>> Greg >>>>> >>>>> On Mon, Oct 31, 2011 at 1:20 PM, Greg Freemyer <gre...@gm...> >>>>> wrote: >>>>>> >>>>>> On Mon, Oct 31, 2011 at 1:04 PM, Amir Goldstein <ami...@gm...> >>>>>> wrote: >>>>>> > On Mon, Oct 31, 2011 at 6:28 PM, Amir Goldstein <ami...@gm...> >>>>>> > wrote: >>>>>> >> On Mon, Oct 31, 2011 at 6:03 PM, Greg Freemyer >>>>>> >> <gre...@gm...> wrote: >>>>>> >>> Amir, >>>>>> >>> >>>>>> >>> We currently have 2 KMP projects to be aware of: >>>>>> >>> >>>>>> >>> "filesystems/ext4dev-snapshots" is the released version which normal >>>>>> >>> testers/people should be downloading from. We need to do our best to >>>>>> >>> keep it usable. >>>>>> >>> >>>>>> >>> "home:next4/ext4dev-snapshots" is the one that should only be used by >>>>>> >>> the next4 team. >>>>>> >>> >>>>>> >>> I just uploaded your new patch to there and will see if it builds. >>>>>> >>> (It was building last week with the old patch, but something happened >>>>>> >>> to factory recently and our KMP no longer builds. >>>>>> >> >>>>>> >> That's my bad. >>>>>> >> the patch ext4dev-trace.patch has an ugly ugly hack. >>>>>> >> it has the absolute path of the OBS BUILD directory hardcoded in the >>>>>> >> patch. >>>>>> >> I just could find another way to make the KMP build properly. >>>>>> >> Now OBS has changed the path from /usr/src/packages/BUILD >>>>>> >> to /home/abuild/rpmbuild/BUILD. >>>>>> >> I will try to fix that by fixing the hardcoded path. >>>>>> >> >>>>>> > >>>>>> > So now the module builds for Factory, but not for Thumbleweed, >>>>>> > which still builds under /usr/src/packages/BUILD :-( >>>>>> > I guess we can live with that problem for now... >>>>>> > >>>>>> > Amir. >>>>>> >>>>>> Tumbleweed will be moving on in the not too distant future to 3.2-rcx >>>>>> etc., so it is not a good target for us. >>>>>> >>>>>> Let's just worry about factory/12.1. 12.1 should stick with 3.1 for >>>>>> the next 18 months. >>>>>> >>>>>> Factory will move on two at some point, so 12.1 is our real target. >>>>>> OBS just doesn't have full 12.1 repo support yet. >>>>>> >>>>>> I'll try to test this build in the next day or so, then push it to the >>>>>> filesystem repo. >>>>>> >>>>>> Greg >>>>> >>>>> >>>>> >>>>> -- >>>>> Greg Freemyer >>>>> Head of EDD Tape Extraction and Processing team >>>>> Litigation Triage Solutions Specialist >>>>> http://www.linkedin.com/in/gregfreemyer >>>>> CNN/TruTV Aired Forensic Imaging Demo - >>>>> >>>>> http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/ >>>>> >>>>> The Norcross Group >>>>> The Intersection of Evidence & Technology >>>>> http://www.norcrossgroup.com >>>>> >>>> >>> >>> >>> >>> -- >>> Greg Freemyer >>> Head of EDD Tape Extraction and Processing team >>> Litigation Triage Solutions Specialist >>> http://www.linkedin.com/in/gregfreemyer >>> CNN/TruTV Aired Forensic Imaging Demo - >>> http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/ >>> >>> The Norcross Group >>> The Intersection of Evidence & Technology >>> http://www.norcrossgroup.com >>> >> > > > > -- > Best Wishes > Yongqiang Yang > |
|
From: Yongqiang Y. <xia...@gm...> - 2011-11-03 03:06:56
|
On Thu, Nov 3, 2011 at 3:22 AM, Amir Goldstein <ami...@gm...> wrote: > On Wed, Nov 2, 2011 at 9:00 PM, Greg Freemyer <gre...@gm...> wrote: >> On Wed, Nov 2, 2011 at 2:54 PM, Amir Goldstein <ami...@gm...> wrote: >>> On Wed, Nov 2, 2011 at 5:17 PM, Greg Freemyer <gre...@gm...> wrote: >>>> Amir, >>>> >>>> I am now running kernel 3.1.0 with the ext4dev-kmp compiled from home:next4. >>> >>> and this is the same kernel that worked fine with the kmp from filesystems repo? >>> >> >> No, that was 3.1.0-RC9 >> >> So this is both a new kernel and newly compiled KMP. > > So maybe just to be sure that we didn't break anything with the merge, > you can try to install the KMP from fs repo. > I think it should run with kernel 3.1... > >> >>>> >>>> I tried xfstests "./check -g auto" from Aditya's git repo. >>>> >>>> It failed on both test 113 and 255. That is on the first pass, so no >>>> snapshots were active. I "assume" that the official ext4 in 3.1.0 doesn't >>>> fail, but I haven't tested it. >>> >>> can you send the detailed error reports of those tests. >> >> I don't find a lot of output for 113, but here's what I have: >> >>> cat 113.out.bad >> QA output created by 113 >> brevity is wit... >> >> ----------------------------------------------- >> aio-stress.1 : -s 120m >> ----------------------------------------------- >> ./113: line 47: 32471 Segmentation fault $here/ltp/aio-stress > > SEGFAULT usually means some IO error, so you should look at dmesg > for errors from ext4dev fs. > >> $_param $AIOSTRESS_AVOID -I $_count $_files >> $tmp.out 2>&1 >> aio-stress (count=1000) returned 0 >> file size 120MB, record size 64KB, depth 64, ios per iteration 8 >> max io_submit 8, buffer alignment set to 4KB >> threads 1 files 1 contexts 1 context offset 2MB verification off >> >> >> >> And for 255 it's >> > > I don't know much about this test, but I reckon Yongqiang knows a lot about it. There are falloc and punch hole tests in 255. It should has nothing to do with snapshot. > > in general I don't like the fact that xfstest is not uptodate. > there have been some bugfixes in xfstest, especially in those 25? tests. Yeah. xfstests has a lot fixes in recent release, especially in fsx. > > Aditya, could you rebase/merge your xfstests repo to recent xfstests. > This probably means changing the test number again... We'd better update to latest xfstests. Three days ago, I updated my xfstests tree to latest one and found a bug in ext4 related to punch hole and the patch has been merged to upstream by Tytso and will appear in 3.2 releases. I am not sure if it is related to this error. Yongqiang. > > Thanks, > Amir. > > > > >>> cat 255.out.bad >> QA output created by 255 >> 1. into a hole >> daa100df6e6711906b61c9ab5aa16032 >> 2. into allocated space >> 0: [0..7]: extent >> 1: [8..23]: hole >> 2: [24..39]: extent >> cc58a7417c2d7763adc45b6fcd3fa024 >> 3. into unwritten space >> daa100df6e6711906b61c9ab5aa16032 >> 4. hole -> data >> 0: [0..23]: hole >> 1: [24..31]: extent >> 2: [32..39]: hole >> cc63069677939f69a6e8f68cae6a6dac >> 5. hole -> unwritten >> daa100df6e6711906b61c9ab5aa16032 >> 6. data -> hole >> 0: [0..7]: extent >> 1: [8..39]: hole >> 1b3779878366498b28c702ef88c4a773 >> 7. data -> unwritten >> 0: [0..7]: extent >> 1: [8..23]: hole >> 2: [24..31]: extent >> 3: [32..39]: hole >> 1b3779878366498b28c702ef88c4a773 >> 8. unwritten -> hole >> daa100df6e6711906b61c9ab5aa16032 >> 9. unwritten -> data >> 0: [0..7]: extent >> 1: [8..23]: hole >> 2: [24..31]: extent >> 3: [32..39]: hole >> cc63069677939f69a6e8f68cae6a6dac >> 10. hole -> data -> hole >> daa100df6e6711906b61c9ab5aa16032 >> 11. data -> hole -> data >> 0: [0..7]: extent >> 1: [8..31]: hole >> 2: [32..39]: extent >> f6aeca13ec49e5b266cd1c913cd726e3 >> 12. unwritten -> data -> unwritten >> 0: [0..7]: extent >> 1: [8..31]: hole >> 2: [32..39]: extent >> daa100df6e6711906b61c9ab5aa16032 >> 13. data -> unwritten -> data >> 0: [0..7]: extent >> 1: [8..31]: hole >> 2: [32..39]: extent >> f6aeca13ec49e5b266cd1c913cd726e3 >> 14. data -> hole @ EOF >> 0: [0..23]: extent >> 1: [24..39]: hole >> e1f024eedd27ea6b1c3e9b841c850404 >> 15. data -> hole @ 0 >> 0: [0..15]: hole >> 1: [16..39]: extent >> eecb7aa303d121835de05028751d301c >> 16. data -> cache cold ->hole >> 0: [0..15]: hole >> 1: [16..39]: extent >> eecb7aa303d121835de05028751d301c >> 17. data -> hole in single block file >> 0: [0..7]: extent >> 13535fd4d496bf0b74bb2335aa4d1b31 >> 1. into a hole >> daa100df6e6711906b61c9ab5aa16032 >> 2. into allocated space >> 0: [0..7]: extent >> 1: [8..23]: hole >> 2: [24..39]: extent >> cc58a7417c2d7763adc45b6fcd3fa024 >> 3. into unwritten space >> daa100df6e6711906b61c9ab5aa16032 >> 4. hole -> data >> 0: [0..23]: hole >> 1: [24..31]: extent >> 2: [32..39]: hole >> cc63069677939f69a6e8f68cae6a6dac >> 5. hole -> unwritten >> daa100df6e6711906b61c9ab5aa16032 >> 6. data -> hole >> 0: [0..7]: extent >> 1: [8..39]: hole >> 1b3779878366498b28c702ef88c4a773 >> 7. data -> unwritten >> 0: [0..7]: extent >> 1: [8..23]: hole >> 2: [24..31]: extent >> 3: [32..39]: hole >> 1b3779878366498b28c702ef88c4a773 >> 8. unwritten -> hole >> daa100df6e6711906b61c9ab5aa16032 >> 9. unwritten -> data >> 0: [0..7]: extent >> 1: [8..23]: hole >> 2: [24..31]: extent >> 3: [32..39]: hole >> cc63069677939f69a6e8f68cae6a6dac >> 10. hole -> data -> hole >> daa100df6e6711906b61c9ab5aa16032 >> 11. data -> hole -> data >> 0: [0..7]: extent >> 1: [8..31]: hole >> 2: [32..39]: extent >> f6aeca13ec49e5b266cd1c913cd726e3 >> 12. unwritten -> data -> unwritten >> 0: [0..7]: extent >> 1: [8..31]: hole >> 2: [32..39]: extent >> daa100df6e6711906b61c9ab5aa16032 >> 13. data -> unwritten -> data >> 0: [0..7]: extent >> 1: [8..31]: hole >> 2: [32..39]: extent >> f6aeca13ec49e5b266cd1c913cd726e3 >> 14. data -> hole @ EOF >> 0: [0..23]: extent >> 1: [24..39]: hole >> e1f024eedd27ea6b1c3e9b841c850404 >> 15. data -> hole @ 0 >> 0: [0..15]: hole >> 1: [16..39]: extent >> eecb7aa303d121835de05028751d301c >> 16. data -> cache cold ->hole >> 0: [0..15]: hole >> 1: [16..39]: extent >> eecb7aa303d121835de05028751d301c >> 17. data -> hole in single block file >> 0: [0..7]: extent >> 13535fd4d496bf0b74bb2335aa4d1b31 >> 1. into a hole >> 5a58e46082be047d0f13bee7974015b9 >> 2. into allocated space >> 0: [0..7]: extent >> 1: [8..23]: hole >> 2: [24..39]: extent >> cc58a7417c2d7763adc45b6fcd3fa024 >> 3. into unwritten space >> cc58a7417c2d7763adc45b6fcd3fa024 >> 4. hole -> data >> 0: [0..7]: extent >> 1: [8..23]: hole >> 2: [24..39]: extent >> cc58a7417c2d7763adc45b6fcd3fa024 >> 5. hole -> unwritten >> cc58a7417c2d7763adc45b6fcd3fa024 >> 6. data -> hole >> 0: [0..7]: extent >> 1: [8..23]: hole >> 2: [24..39]: extent >> cc58a7417c2d7763adc45b6fcd3fa024 >> 7. data -> unwritten >> 0: [0..7]: extent >> 1: [8..23]: hole >> 2: [24..39]: extent >> cc58a7417c2d7763adc45b6fcd3fa024 >> 8. unwritten -> hole >> cc58a7417c2d7763adc45b6fcd3fa024 >> 9. unwritten -> data >> 0: [0..7]: extent >> 1: [8..23]: hole >> 2: [24..39]: extent >> cc58a7417c2d7763adc45b6fcd3fa024 >> 10. hole -> data -> hole >> 0: [0..7]: extent >> 1: [8..31]: hole >> 2: [32..39]: extent >> f6aeca13ec49e5b266cd1c913cd726e3 >> 11. data -> hole -> data >> 0: [0..7]: extent >> 1: [8..31]: hole >> 2: [32..39]: extent >> f6aeca13ec49e5b266cd1c913cd726e3 >> 12. unwritten -> data -> unwritten >> 0: [0..7]: extent >> 1: [8..31]: hole >> 2: [32..39]: extent >> f6aeca13ec49e5b266cd1c913cd726e3 >> 13. data -> unwritten -> data >> 0: [0..7]: extent >> 1: [8..31]: hole >> 2: [32..39]: extent >> f6aeca13ec49e5b266cd1c913cd726e3 >> 14. data -> hole @ EOF >> 0: [0..23]: extent >> 1: [24..39]: hole >> e1f024eedd27ea6b1c3e9b841c850404 >> 15. data -> hole @ 0 >> 0: [0..15]: hole >> 1: [16..39]: extent >> eecb7aa303d121835de05028751d301c >> 16. data -> cache cold ->hole >> 0: [0..15]: hole >> 1: [16..39]: extent >> eecb7aa303d121835de05028751d301c >> 17. data -> hole in single block file >> 0: [0..7]: extent >> 13535fd4d496bf0b74bb2335aa4d1b31 >> 1. into a hole >> 5a58e46082be047d0f13bee7974015b9 >> 2. into allocated space >> 0: [0..7]: extent >> 1: [8..23]: hole >> 2: [24..39]: extent >> cc58a7417c2d7763adc45b6fcd3fa024 >> 3. into unwritten space >> cc58a7417c2d7763adc45b6fcd3fa024 >> 4. hole -> data >> 0: [0..7]: extent >> 1: [8..23]: hole >> 2: [24..39]: extent >> cc58a7417c2d7763adc45b6fcd3fa024 >> 5. hole -> unwritten >> cc58a7417c2d7763adc45b6fcd3fa024 >> 6. data -> hole >> 0: [0..7]: extent >> 1: [8..23]: hole >> 2: [24..39]: extent >> cc58a7417c2d7763adc45b6fcd3fa024 >> 7. data -> unwritten >> 0: [0..7]: extent >> 1: [8..23]: hole >> 2: [24..39]: extent >> cc58a7417c2d7763adc45b6fcd3fa024 >> 8. unwritten -> hole >> cc58a7417c2d7763adc45b6fcd3fa024 >> 9. unwritten -> data >> 0: [0..7]: extent >> 1: [8..23]: hole >> 2: [24..39]: extent >> cc58a7417c2d7763adc45b6fcd3fa024 >> 10. hole -> data -> hole >> 0: [0..7]: extent >> 1: [8..31]: hole >> 2: [32..39]: extent >> f6aeca13ec49e5b266cd1c913cd726e3 >> 11. data -> hole -> data >> 0: [0..7]: extent >> 1: [8..31]: hole >> 2: [32..39]: extent >> f6aeca13ec49e5b266cd1c913cd726e3 >> 12. unwritten -> data -> unwritten >> 0: [0..7]: extent >> 1: [8..31]: hole >> 2: [32..39]: extent >> f6aeca13ec49e5b266cd1c913cd726e3 >> 13. data -> unwritten -> data >> 0: [0..7]: extent >> 1: [8..31]: hole >> 2: [32..39]: extent >> f6aeca13ec49e5b266cd1c913cd726e3 >> 14. data -> hole @ EOF >> 0: [0..23]: extent >> 1: [24..39]: hole >> e1f024eedd27ea6b1c3e9b841c850404 >> 15. data -> hole @ 0 >> 0: [0..15]: hole >> 1: [16..39]: extent >> eecb7aa303d121835de05028751d301c >> 16. data -> cache cold ->hole >> 0: [0..15]: hole >> 1: [16..39]: extent >> eecb7aa303d121835de05028751d301c >> 17. data -> hole in single block file >> 0: [0..7]: extent >> 13535fd4d496bf0b74bb2335aa4d1b31 >> >> >> >> Greg >> >>> >>> Thanks, >>> Amir. >>> >>>> >>>> Greg >>>> >>>> On Mon, Oct 31, 2011 at 1:20 PM, Greg Freemyer <gre...@gm...> >>>> wrote: >>>>> >>>>> On Mon, Oct 31, 2011 at 1:04 PM, Amir Goldstein <ami...@gm...> >>>>> wrote: >>>>> > On Mon, Oct 31, 2011 at 6:28 PM, Amir Goldstein <ami...@gm...> >>>>> > wrote: >>>>> >> On Mon, Oct 31, 2011 at 6:03 PM, Greg Freemyer >>>>> >> <gre...@gm...> wrote: >>>>> >>> Amir, >>>>> >>> >>>>> >>> We currently have 2 KMP projects to be aware of: >>>>> >>> >>>>> >>> "filesystems/ext4dev-snapshots" is the released version which normal >>>>> >>> testers/people should be downloading from. We need to do our best to >>>>> >>> keep it usable. >>>>> >>> >>>>> >>> "home:next4/ext4dev-snapshots" is the one that should only be used by >>>>> >>> the next4 team. >>>>> >>> >>>>> >>> I just uploaded your new patch to there and will see if it builds. >>>>> >>> (It was building last week with the old patch, but something happened >>>>> >>> to factory recently and our KMP no longer builds. >>>>> >> >>>>> >> That's my bad. >>>>> >> the patch ext4dev-trace.patch has an ugly ugly hack. >>>>> >> it has the absolute path of the OBS BUILD directory hardcoded in the >>>>> >> patch. >>>>> >> I just could find another way to make the KMP build properly. >>>>> >> Now OBS has changed the path from /usr/src/packages/BUILD >>>>> >> to /home/abuild/rpmbuild/BUILD. >>>>> >> I will try to fix that by fixing the hardcoded path. >>>>> >> >>>>> > >>>>> > So now the module builds for Factory, but not for Thumbleweed, >>>>> > which still builds under /usr/src/packages/BUILD :-( >>>>> > I guess we can live with that problem for now... >>>>> > >>>>> > Amir. >>>>> >>>>> Tumbleweed will be moving on in the not too distant future to 3.2-rcx >>>>> etc., so it is not a good target for us. >>>>> >>>>> Let's just worry about factory/12.1. 12.1 should stick with 3.1 for >>>>> the next 18 months. >>>>> >>>>> Factory will move on two at some point, so 12.1 is our real target. >>>>> OBS just doesn't have full 12.1 repo support yet. >>>>> >>>>> I'll try to test this build in the next day or so, then push it to the >>>>> filesystem repo. >>>>> >>>>> Greg >>>> >>>> >>>> >>>> -- >>>> Greg Freemyer >>>> Head of EDD Tape Extraction and Processing team >>>> Litigation Triage Solutions Specialist >>>> http://www.linkedin.com/in/gregfreemyer >>>> CNN/TruTV Aired Forensic Imaging Demo - >>>> >>>> http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/ >>>> >>>> The Norcross Group >>>> The Intersection of Evidence & Technology >>>> http://www.norcrossgroup.com >>>> >>> >> >> >> >> -- >> Greg Freemyer >> Head of EDD Tape Extraction and Processing team >> Litigation Triage Solutions Specialist >> http://www.linkedin.com/in/gregfreemyer >> CNN/TruTV Aired Forensic Imaging Demo - >> http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/ >> >> The Norcross Group >> The Intersection of Evidence & Technology >> http://www.norcrossgroup.com >> > -- Best Wishes Yongqiang Yang |
|
From: Amir G. <ami...@gm...> - 2011-11-02 19:23:05
|
On Wed, Nov 2, 2011 at 9:00 PM, Greg Freemyer <gre...@gm...> wrote: > On Wed, Nov 2, 2011 at 2:54 PM, Amir Goldstein <ami...@gm...> wrote: >> On Wed, Nov 2, 2011 at 5:17 PM, Greg Freemyer <gre...@gm...> wrote: >>> Amir, >>> >>> I am now running kernel 3.1.0 with the ext4dev-kmp compiled from home:next4. >> >> and this is the same kernel that worked fine with the kmp from filesystems repo? >> > > No, that was 3.1.0-RC9 > > So this is both a new kernel and newly compiled KMP. So maybe just to be sure that we didn't break anything with the merge, you can try to install the KMP from fs repo. I think it should run with kernel 3.1... > >>> >>> I tried xfstests "./check -g auto" from Aditya's git repo. >>> >>> It failed on both test 113 and 255. That is on the first pass, so no >>> snapshots were active. I "assume" that the official ext4 in 3.1.0 doesn't >>> fail, but I haven't tested it. >> >> can you send the detailed error reports of those tests. > > I don't find a lot of output for 113, but here's what I have: > >> cat 113.out.bad > QA output created by 113 > brevity is wit... > > ----------------------------------------------- > aio-stress.1 : -s 120m > ----------------------------------------------- > ./113: line 47: 32471 Segmentation fault $here/ltp/aio-stress SEGFAULT usually means some IO error, so you should look at dmesg for errors from ext4dev fs. > $_param $AIOSTRESS_AVOID -I $_count $_files >> $tmp.out 2>&1 > aio-stress (count=1000) returned 0 > file size 120MB, record size 64KB, depth 64, ios per iteration 8 > max io_submit 8, buffer alignment set to 4KB > threads 1 files 1 contexts 1 context offset 2MB verification off > > > > And for 255 it's > I don't know much about this test, but I reckon Yongqiang knows a lot about it. in general I don't like the fact that xfstest is not uptodate. there have been some bugfixes in xfstest, especially in those 25? tests. Aditya, could you rebase/merge your xfstests repo to recent xfstests. This probably means changing the test number again... Thanks, Amir. >> cat 255.out.bad > QA output created by 255 > 1. into a hole > daa100df6e6711906b61c9ab5aa16032 > 2. into allocated space > 0: [0..7]: extent > 1: [8..23]: hole > 2: [24..39]: extent > cc58a7417c2d7763adc45b6fcd3fa024 > 3. into unwritten space > daa100df6e6711906b61c9ab5aa16032 > 4. hole -> data > 0: [0..23]: hole > 1: [24..31]: extent > 2: [32..39]: hole > cc63069677939f69a6e8f68cae6a6dac > 5. hole -> unwritten > daa100df6e6711906b61c9ab5aa16032 > 6. data -> hole > 0: [0..7]: extent > 1: [8..39]: hole > 1b3779878366498b28c702ef88c4a773 > 7. data -> unwritten > 0: [0..7]: extent > 1: [8..23]: hole > 2: [24..31]: extent > 3: [32..39]: hole > 1b3779878366498b28c702ef88c4a773 > 8. unwritten -> hole > daa100df6e6711906b61c9ab5aa16032 > 9. unwritten -> data > 0: [0..7]: extent > 1: [8..23]: hole > 2: [24..31]: extent > 3: [32..39]: hole > cc63069677939f69a6e8f68cae6a6dac > 10. hole -> data -> hole > daa100df6e6711906b61c9ab5aa16032 > 11. data -> hole -> data > 0: [0..7]: extent > 1: [8..31]: hole > 2: [32..39]: extent > f6aeca13ec49e5b266cd1c913cd726e3 > 12. unwritten -> data -> unwritten > 0: [0..7]: extent > 1: [8..31]: hole > 2: [32..39]: extent > daa100df6e6711906b61c9ab5aa16032 > 13. data -> unwritten -> data > 0: [0..7]: extent > 1: [8..31]: hole > 2: [32..39]: extent > f6aeca13ec49e5b266cd1c913cd726e3 > 14. data -> hole @ EOF > 0: [0..23]: extent > 1: [24..39]: hole > e1f024eedd27ea6b1c3e9b841c850404 > 15. data -> hole @ 0 > 0: [0..15]: hole > 1: [16..39]: extent > eecb7aa303d121835de05028751d301c > 16. data -> cache cold ->hole > 0: [0..15]: hole > 1: [16..39]: extent > eecb7aa303d121835de05028751d301c > 17. data -> hole in single block file > 0: [0..7]: extent > 13535fd4d496bf0b74bb2335aa4d1b31 > 1. into a hole > daa100df6e6711906b61c9ab5aa16032 > 2. into allocated space > 0: [0..7]: extent > 1: [8..23]: hole > 2: [24..39]: extent > cc58a7417c2d7763adc45b6fcd3fa024 > 3. into unwritten space > daa100df6e6711906b61c9ab5aa16032 > 4. hole -> data > 0: [0..23]: hole > 1: [24..31]: extent > 2: [32..39]: hole > cc63069677939f69a6e8f68cae6a6dac > 5. hole -> unwritten > daa100df6e6711906b61c9ab5aa16032 > 6. data -> hole > 0: [0..7]: extent > 1: [8..39]: hole > 1b3779878366498b28c702ef88c4a773 > 7. data -> unwritten > 0: [0..7]: extent > 1: [8..23]: hole > 2: [24..31]: extent > 3: [32..39]: hole > 1b3779878366498b28c702ef88c4a773 > 8. unwritten -> hole > daa100df6e6711906b61c9ab5aa16032 > 9. unwritten -> data > 0: [0..7]: extent > 1: [8..23]: hole > 2: [24..31]: extent > 3: [32..39]: hole > cc63069677939f69a6e8f68cae6a6dac > 10. hole -> data -> hole > daa100df6e6711906b61c9ab5aa16032 > 11. data -> hole -> data > 0: [0..7]: extent > 1: [8..31]: hole > 2: [32..39]: extent > f6aeca13ec49e5b266cd1c913cd726e3 > 12. unwritten -> data -> unwritten > 0: [0..7]: extent > 1: [8..31]: hole > 2: [32..39]: extent > daa100df6e6711906b61c9ab5aa16032 > 13. data -> unwritten -> data > 0: [0..7]: extent > 1: [8..31]: hole > 2: [32..39]: extent > f6aeca13ec49e5b266cd1c913cd726e3 > 14. data -> hole @ EOF > 0: [0..23]: extent > 1: [24..39]: hole > e1f024eedd27ea6b1c3e9b841c850404 > 15. data -> hole @ 0 > 0: [0..15]: hole > 1: [16..39]: extent > eecb7aa303d121835de05028751d301c > 16. data -> cache cold ->hole > 0: [0..15]: hole > 1: [16..39]: extent > eecb7aa303d121835de05028751d301c > 17. data -> hole in single block file > 0: [0..7]: extent > 13535fd4d496bf0b74bb2335aa4d1b31 > 1. into a hole > 5a58e46082be047d0f13bee7974015b9 > 2. into allocated space > 0: [0..7]: extent > 1: [8..23]: hole > 2: [24..39]: extent > cc58a7417c2d7763adc45b6fcd3fa024 > 3. into unwritten space > cc58a7417c2d7763adc45b6fcd3fa024 > 4. hole -> data > 0: [0..7]: extent > 1: [8..23]: hole > 2: [24..39]: extent > cc58a7417c2d7763adc45b6fcd3fa024 > 5. hole -> unwritten > cc58a7417c2d7763adc45b6fcd3fa024 > 6. data -> hole > 0: [0..7]: extent > 1: [8..23]: hole > 2: [24..39]: extent > cc58a7417c2d7763adc45b6fcd3fa024 > 7. data -> unwritten > 0: [0..7]: extent > 1: [8..23]: hole > 2: [24..39]: extent > cc58a7417c2d7763adc45b6fcd3fa024 > 8. unwritten -> hole > cc58a7417c2d7763adc45b6fcd3fa024 > 9. unwritten -> data > 0: [0..7]: extent > 1: [8..23]: hole > 2: [24..39]: extent > cc58a7417c2d7763adc45b6fcd3fa024 > 10. hole -> data -> hole > 0: [0..7]: extent > 1: [8..31]: hole > 2: [32..39]: extent > f6aeca13ec49e5b266cd1c913cd726e3 > 11. data -> hole -> data > 0: [0..7]: extent > 1: [8..31]: hole > 2: [32..39]: extent > f6aeca13ec49e5b266cd1c913cd726e3 > 12. unwritten -> data -> unwritten > 0: [0..7]: extent > 1: [8..31]: hole > 2: [32..39]: extent > f6aeca13ec49e5b266cd1c913cd726e3 > 13. data -> unwritten -> data > 0: [0..7]: extent > 1: [8..31]: hole > 2: [32..39]: extent > f6aeca13ec49e5b266cd1c913cd726e3 > 14. data -> hole @ EOF > 0: [0..23]: extent > 1: [24..39]: hole > e1f024eedd27ea6b1c3e9b841c850404 > 15. data -> hole @ 0 > 0: [0..15]: hole > 1: [16..39]: extent > eecb7aa303d121835de05028751d301c > 16. data -> cache cold ->hole > 0: [0..15]: hole > 1: [16..39]: extent > eecb7aa303d121835de05028751d301c > 17. data -> hole in single block file > 0: [0..7]: extent > 13535fd4d496bf0b74bb2335aa4d1b31 > 1. into a hole > 5a58e46082be047d0f13bee7974015b9 > 2. into allocated space > 0: [0..7]: extent > 1: [8..23]: hole > 2: [24..39]: extent > cc58a7417c2d7763adc45b6fcd3fa024 > 3. into unwritten space > cc58a7417c2d7763adc45b6fcd3fa024 > 4. hole -> data > 0: [0..7]: extent > 1: [8..23]: hole > 2: [24..39]: extent > cc58a7417c2d7763adc45b6fcd3fa024 > 5. hole -> unwritten > cc58a7417c2d7763adc45b6fcd3fa024 > 6. data -> hole > 0: [0..7]: extent > 1: [8..23]: hole > 2: [24..39]: extent > cc58a7417c2d7763adc45b6fcd3fa024 > 7. data -> unwritten > 0: [0..7]: extent > 1: [8..23]: hole > 2: [24..39]: extent > cc58a7417c2d7763adc45b6fcd3fa024 > 8. unwritten -> hole > cc58a7417c2d7763adc45b6fcd3fa024 > 9. unwritten -> data > 0: [0..7]: extent > 1: [8..23]: hole > 2: [24..39]: extent > cc58a7417c2d7763adc45b6fcd3fa024 > 10. hole -> data -> hole > 0: [0..7]: extent > 1: [8..31]: hole > 2: [32..39]: extent > f6aeca13ec49e5b266cd1c913cd726e3 > 11. data -> hole -> data > 0: [0..7]: extent > 1: [8..31]: hole > 2: [32..39]: extent > f6aeca13ec49e5b266cd1c913cd726e3 > 12. unwritten -> data -> unwritten > 0: [0..7]: extent > 1: [8..31]: hole > 2: [32..39]: extent > f6aeca13ec49e5b266cd1c913cd726e3 > 13. data -> unwritten -> data > 0: [0..7]: extent > 1: [8..31]: hole > 2: [32..39]: extent > f6aeca13ec49e5b266cd1c913cd726e3 > 14. data -> hole @ EOF > 0: [0..23]: extent > 1: [24..39]: hole > e1f024eedd27ea6b1c3e9b841c850404 > 15. data -> hole @ 0 > 0: [0..15]: hole > 1: [16..39]: extent > eecb7aa303d121835de05028751d301c > 16. data -> cache cold ->hole > 0: [0..15]: hole > 1: [16..39]: extent > eecb7aa303d121835de05028751d301c > 17. data -> hole in single block file > 0: [0..7]: extent > 13535fd4d496bf0b74bb2335aa4d1b31 > > > > Greg > >> >> Thanks, >> Amir. >> >>> >>> Greg >>> >>> On Mon, Oct 31, 2011 at 1:20 PM, Greg Freemyer <gre...@gm...> >>> wrote: >>>> >>>> On Mon, Oct 31, 2011 at 1:04 PM, Amir Goldstein <ami...@gm...> >>>> wrote: >>>> > On Mon, Oct 31, 2011 at 6:28 PM, Amir Goldstein <ami...@gm...> >>>> > wrote: >>>> >> On Mon, Oct 31, 2011 at 6:03 PM, Greg Freemyer >>>> >> <gre...@gm...> wrote: >>>> >>> Amir, >>>> >>> >>>> >>> We currently have 2 KMP projects to be aware of: >>>> >>> >>>> >>> "filesystems/ext4dev-snapshots" is the released version which normal >>>> >>> testers/people should be downloading from. We need to do our best to >>>> >>> keep it usable. >>>> >>> >>>> >>> "home:next4/ext4dev-snapshots" is the one that should only be used by >>>> >>> the next4 team. >>>> >>> >>>> >>> I just uploaded your new patch to there and will see if it builds. >>>> >>> (It was building last week with the old patch, but something happened >>>> >>> to factory recently and our KMP no longer builds. >>>> >> >>>> >> That's my bad. >>>> >> the patch ext4dev-trace.patch has an ugly ugly hack. >>>> >> it has the absolute path of the OBS BUILD directory hardcoded in the >>>> >> patch. >>>> >> I just could find another way to make the KMP build properly. >>>> >> Now OBS has changed the path from /usr/src/packages/BUILD >>>> >> to /home/abuild/rpmbuild/BUILD. >>>> >> I will try to fix that by fixing the hardcoded path. >>>> >> >>>> > >>>> > So now the module builds for Factory, but not for Thumbleweed, >>>> > which still builds under /usr/src/packages/BUILD :-( >>>> > I guess we can live with that problem for now... >>>> > >>>> > Amir. >>>> >>>> Tumbleweed will be moving on in the not too distant future to 3.2-rcx >>>> etc., so it is not a good target for us. >>>> >>>> Let's just worry about factory/12.1. 12.1 should stick with 3.1 for >>>> the next 18 months. >>>> >>>> Factory will move on two at some point, so 12.1 is our real target. >>>> OBS just doesn't have full 12.1 repo support yet. >>>> >>>> I'll try to test this build in the next day or so, then push it to the >>>> filesystem repo. >>>> >>>> Greg >>> >>> >>> >>> -- >>> Greg Freemyer >>> Head of EDD Tape Extraction and Processing team >>> Litigation Triage Solutions Specialist >>> http://www.linkedin.com/in/gregfreemyer >>> CNN/TruTV Aired Forensic Imaging Demo - >>> >>> http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/ >>> >>> The Norcross Group >>> The Intersection of Evidence & Technology >>> http://www.norcrossgroup.com >>> >> > > > > -- > Greg Freemyer > Head of EDD Tape Extraction and Processing team > Litigation Triage Solutions Specialist > http://www.linkedin.com/in/gregfreemyer > CNN/TruTV Aired Forensic Imaging Demo - > http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/ > > The Norcross Group > The Intersection of Evidence & Technology > http://www.norcrossgroup.com > |
|
From: Greg F. <gre...@gm...> - 2011-11-02 19:01:12
|
On Wed, Nov 2, 2011 at 2:54 PM, Amir Goldstein <ami...@gm...> wrote:
> On Wed, Nov 2, 2011 at 5:17 PM, Greg Freemyer <gre...@gm...> wrote:
>> Amir,
>>
>> I am now running kernel 3.1.0 with the ext4dev-kmp compiled from home:next4.
>
> and this is the same kernel that worked fine with the kmp from filesystems repo?
>
No, that was 3.1.0-RC9
So this is both a new kernel and newly compiled KMP.
>>
>> I tried xfstests "./check -g auto" from Aditya's git repo.
>>
>> It failed on both test 113 and 255. That is on the first pass, so no
>> snapshots were active. I "assume" that the official ext4 in 3.1.0 doesn't
>> fail, but I haven't tested it.
>
> can you send the detailed error reports of those tests.
I don't find a lot of output for 113, but here's what I have:
> cat 113.out.bad
QA output created by 113
brevity is wit...
-----------------------------------------------
aio-stress.1 : -s 120m
-----------------------------------------------
./113: line 47: 32471 Segmentation fault $here/ltp/aio-stress
$_param $AIOSTRESS_AVOID -I $_count $_files >> $tmp.out 2>&1
aio-stress (count=1000) returned 0
file size 120MB, record size 64KB, depth 64, ios per iteration 8
max io_submit 8, buffer alignment set to 4KB
threads 1 files 1 contexts 1 context offset 2MB verification off
And for 255 it's
> cat 255.out.bad
QA output created by 255
1. into a hole
daa100df6e6711906b61c9ab5aa16032
2. into allocated space
0: [0..7]: extent
1: [8..23]: hole
2: [24..39]: extent
cc58a7417c2d7763adc45b6fcd3fa024
3. into unwritten space
daa100df6e6711906b61c9ab5aa16032
4. hole -> data
0: [0..23]: hole
1: [24..31]: extent
2: [32..39]: hole
cc63069677939f69a6e8f68cae6a6dac
5. hole -> unwritten
daa100df6e6711906b61c9ab5aa16032
6. data -> hole
0: [0..7]: extent
1: [8..39]: hole
1b3779878366498b28c702ef88c4a773
7. data -> unwritten
0: [0..7]: extent
1: [8..23]: hole
2: [24..31]: extent
3: [32..39]: hole
1b3779878366498b28c702ef88c4a773
8. unwritten -> hole
daa100df6e6711906b61c9ab5aa16032
9. unwritten -> data
0: [0..7]: extent
1: [8..23]: hole
2: [24..31]: extent
3: [32..39]: hole
cc63069677939f69a6e8f68cae6a6dac
10. hole -> data -> hole
daa100df6e6711906b61c9ab5aa16032
11. data -> hole -> data
0: [0..7]: extent
1: [8..31]: hole
2: [32..39]: extent
f6aeca13ec49e5b266cd1c913cd726e3
12. unwritten -> data -> unwritten
0: [0..7]: extent
1: [8..31]: hole
2: [32..39]: extent
daa100df6e6711906b61c9ab5aa16032
13. data -> unwritten -> data
0: [0..7]: extent
1: [8..31]: hole
2: [32..39]: extent
f6aeca13ec49e5b266cd1c913cd726e3
14. data -> hole @ EOF
0: [0..23]: extent
1: [24..39]: hole
e1f024eedd27ea6b1c3e9b841c850404
15. data -> hole @ 0
0: [0..15]: hole
1: [16..39]: extent
eecb7aa303d121835de05028751d301c
16. data -> cache cold ->hole
0: [0..15]: hole
1: [16..39]: extent
eecb7aa303d121835de05028751d301c
17. data -> hole in single block file
0: [0..7]: extent
13535fd4d496bf0b74bb2335aa4d1b31
1. into a hole
daa100df6e6711906b61c9ab5aa16032
2. into allocated space
0: [0..7]: extent
1: [8..23]: hole
2: [24..39]: extent
cc58a7417c2d7763adc45b6fcd3fa024
3. into unwritten space
daa100df6e6711906b61c9ab5aa16032
4. hole -> data
0: [0..23]: hole
1: [24..31]: extent
2: [32..39]: hole
cc63069677939f69a6e8f68cae6a6dac
5. hole -> unwritten
daa100df6e6711906b61c9ab5aa16032
6. data -> hole
0: [0..7]: extent
1: [8..39]: hole
1b3779878366498b28c702ef88c4a773
7. data -> unwritten
0: [0..7]: extent
1: [8..23]: hole
2: [24..31]: extent
3: [32..39]: hole
1b3779878366498b28c702ef88c4a773
8. unwritten -> hole
daa100df6e6711906b61c9ab5aa16032
9. unwritten -> data
0: [0..7]: extent
1: [8..23]: hole
2: [24..31]: extent
3: [32..39]: hole
cc63069677939f69a6e8f68cae6a6dac
10. hole -> data -> hole
daa100df6e6711906b61c9ab5aa16032
11. data -> hole -> data
0: [0..7]: extent
1: [8..31]: hole
2: [32..39]: extent
f6aeca13ec49e5b266cd1c913cd726e3
12. unwritten -> data -> unwritten
0: [0..7]: extent
1: [8..31]: hole
2: [32..39]: extent
daa100df6e6711906b61c9ab5aa16032
13. data -> unwritten -> data
0: [0..7]: extent
1: [8..31]: hole
2: [32..39]: extent
f6aeca13ec49e5b266cd1c913cd726e3
14. data -> hole @ EOF
0: [0..23]: extent
1: [24..39]: hole
e1f024eedd27ea6b1c3e9b841c850404
15. data -> hole @ 0
0: [0..15]: hole
1: [16..39]: extent
eecb7aa303d121835de05028751d301c
16. data -> cache cold ->hole
0: [0..15]: hole
1: [16..39]: extent
eecb7aa303d121835de05028751d301c
17. data -> hole in single block file
0: [0..7]: extent
13535fd4d496bf0b74bb2335aa4d1b31
1. into a hole
5a58e46082be047d0f13bee7974015b9
2. into allocated space
0: [0..7]: extent
1: [8..23]: hole
2: [24..39]: extent
cc58a7417c2d7763adc45b6fcd3fa024
3. into unwritten space
cc58a7417c2d7763adc45b6fcd3fa024
4. hole -> data
0: [0..7]: extent
1: [8..23]: hole
2: [24..39]: extent
cc58a7417c2d7763adc45b6fcd3fa024
5. hole -> unwritten
cc58a7417c2d7763adc45b6fcd3fa024
6. data -> hole
0: [0..7]: extent
1: [8..23]: hole
2: [24..39]: extent
cc58a7417c2d7763adc45b6fcd3fa024
7. data -> unwritten
0: [0..7]: extent
1: [8..23]: hole
2: [24..39]: extent
cc58a7417c2d7763adc45b6fcd3fa024
8. unwritten -> hole
cc58a7417c2d7763adc45b6fcd3fa024
9. unwritten -> data
0: [0..7]: extent
1: [8..23]: hole
2: [24..39]: extent
cc58a7417c2d7763adc45b6fcd3fa024
10. hole -> data -> hole
0: [0..7]: extent
1: [8..31]: hole
2: [32..39]: extent
f6aeca13ec49e5b266cd1c913cd726e3
11. data -> hole -> data
0: [0..7]: extent
1: [8..31]: hole
2: [32..39]: extent
f6aeca13ec49e5b266cd1c913cd726e3
12. unwritten -> data -> unwritten
0: [0..7]: extent
1: [8..31]: hole
2: [32..39]: extent
f6aeca13ec49e5b266cd1c913cd726e3
13. data -> unwritten -> data
0: [0..7]: extent
1: [8..31]: hole
2: [32..39]: extent
f6aeca13ec49e5b266cd1c913cd726e3
14. data -> hole @ EOF
0: [0..23]: extent
1: [24..39]: hole
e1f024eedd27ea6b1c3e9b841c850404
15. data -> hole @ 0
0: [0..15]: hole
1: [16..39]: extent
eecb7aa303d121835de05028751d301c
16. data -> cache cold ->hole
0: [0..15]: hole
1: [16..39]: extent
eecb7aa303d121835de05028751d301c
17. data -> hole in single block file
0: [0..7]: extent
13535fd4d496bf0b74bb2335aa4d1b31
1. into a hole
5a58e46082be047d0f13bee7974015b9
2. into allocated space
0: [0..7]: extent
1: [8..23]: hole
2: [24..39]: extent
cc58a7417c2d7763adc45b6fcd3fa024
3. into unwritten space
cc58a7417c2d7763adc45b6fcd3fa024
4. hole -> data
0: [0..7]: extent
1: [8..23]: hole
2: [24..39]: extent
cc58a7417c2d7763adc45b6fcd3fa024
5. hole -> unwritten
cc58a7417c2d7763adc45b6fcd3fa024
6. data -> hole
0: [0..7]: extent
1: [8..23]: hole
2: [24..39]: extent
cc58a7417c2d7763adc45b6fcd3fa024
7. data -> unwritten
0: [0..7]: extent
1: [8..23]: hole
2: [24..39]: extent
cc58a7417c2d7763adc45b6fcd3fa024
8. unwritten -> hole
cc58a7417c2d7763adc45b6fcd3fa024
9. unwritten -> data
0: [0..7]: extent
1: [8..23]: hole
2: [24..39]: extent
cc58a7417c2d7763adc45b6fcd3fa024
10. hole -> data -> hole
0: [0..7]: extent
1: [8..31]: hole
2: [32..39]: extent
f6aeca13ec49e5b266cd1c913cd726e3
11. data -> hole -> data
0: [0..7]: extent
1: [8..31]: hole
2: [32..39]: extent
f6aeca13ec49e5b266cd1c913cd726e3
12. unwritten -> data -> unwritten
0: [0..7]: extent
1: [8..31]: hole
2: [32..39]: extent
f6aeca13ec49e5b266cd1c913cd726e3
13. data -> unwritten -> data
0: [0..7]: extent
1: [8..31]: hole
2: [32..39]: extent
f6aeca13ec49e5b266cd1c913cd726e3
14. data -> hole @ EOF
0: [0..23]: extent
1: [24..39]: hole
e1f024eedd27ea6b1c3e9b841c850404
15. data -> hole @ 0
0: [0..15]: hole
1: [16..39]: extent
eecb7aa303d121835de05028751d301c
16. data -> cache cold ->hole
0: [0..15]: hole
1: [16..39]: extent
eecb7aa303d121835de05028751d301c
17. data -> hole in single block file
0: [0..7]: extent
13535fd4d496bf0b74bb2335aa4d1b31
Greg
>
> Thanks,
> Amir.
>
>>
>> Greg
>>
>> On Mon, Oct 31, 2011 at 1:20 PM, Greg Freemyer <gre...@gm...>
>> wrote:
>>>
>>> On Mon, Oct 31, 2011 at 1:04 PM, Amir Goldstein <ami...@gm...>
>>> wrote:
>>> > On Mon, Oct 31, 2011 at 6:28 PM, Amir Goldstein <ami...@gm...>
>>> > wrote:
>>> >> On Mon, Oct 31, 2011 at 6:03 PM, Greg Freemyer
>>> >> <gre...@gm...> wrote:
>>> >>> Amir,
>>> >>>
>>> >>> We currently have 2 KMP projects to be aware of:
>>> >>>
>>> >>> "filesystems/ext4dev-snapshots" is the released version which normal
>>> >>> testers/people should be downloading from. We need to do our best to
>>> >>> keep it usable.
>>> >>>
>>> >>> "home:next4/ext4dev-snapshots" is the one that should only be used by
>>> >>> the next4 team.
>>> >>>
>>> >>> I just uploaded your new patch to there and will see if it builds.
>>> >>> (It was building last week with the old patch, but something happened
>>> >>> to factory recently and our KMP no longer builds.
>>> >>
>>> >> That's my bad.
>>> >> the patch ext4dev-trace.patch has an ugly ugly hack.
>>> >> it has the absolute path of the OBS BUILD directory hardcoded in the
>>> >> patch.
>>> >> I just could find another way to make the KMP build properly.
>>> >> Now OBS has changed the path from /usr/src/packages/BUILD
>>> >> to /home/abuild/rpmbuild/BUILD.
>>> >> I will try to fix that by fixing the hardcoded path.
>>> >>
>>> >
>>> > So now the module builds for Factory, but not for Thumbleweed,
>>> > which still builds under /usr/src/packages/BUILD :-(
>>> > I guess we can live with that problem for now...
>>> >
>>> > Amir.
>>>
>>> Tumbleweed will be moving on in the not too distant future to 3.2-rcx
>>> etc., so it is not a good target for us.
>>>
>>> Let's just worry about factory/12.1. 12.1 should stick with 3.1 for
>>> the next 18 months.
>>>
>>> Factory will move on two at some point, so 12.1 is our real target.
>>> OBS just doesn't have full 12.1 repo support yet.
>>>
>>> I'll try to test this build in the next day or so, then push it to the
>>> filesystem repo.
>>>
>>> Greg
>>
>>
>>
>> --
>> Greg Freemyer
>> Head of EDD Tape Extraction and Processing team
>> Litigation Triage Solutions Specialist
>> http://www.linkedin.com/in/gregfreemyer
>> CNN/TruTV Aired Forensic Imaging Demo -
>>
>> http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/
>>
>> The Norcross Group
>> The Intersection of Evidence & Technology
>> http://www.norcrossgroup.com
>>
>
--
Greg Freemyer
Head of EDD Tape Extraction and Processing team
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
CNN/TruTV Aired Forensic Imaging Demo -
http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/
The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com
|
|
From: Amir G. <ami...@gm...> - 2011-11-02 18:54:33
|
On Wed, Nov 2, 2011 at 5:17 PM, Greg Freemyer <gre...@gm...> wrote: > Amir, > > I am now running kernel 3.1.0 with the ext4dev-kmp compiled from home:next4. and this is the same kernel that worked fine with the kmp from filesystems repo? > > I tried xfstests "./check -g auto" from Aditya's git repo. > > It failed on both test 113 and 255. That is on the first pass, so no > snapshots were active. I "assume" that the official ext4 in 3.1.0 doesn't > fail, but I haven't tested it. can you send the detailed error reports of those tests. Thanks, Amir. > > Greg > > On Mon, Oct 31, 2011 at 1:20 PM, Greg Freemyer <gre...@gm...> > wrote: >> >> On Mon, Oct 31, 2011 at 1:04 PM, Amir Goldstein <ami...@gm...> >> wrote: >> > On Mon, Oct 31, 2011 at 6:28 PM, Amir Goldstein <ami...@gm...> >> > wrote: >> >> On Mon, Oct 31, 2011 at 6:03 PM, Greg Freemyer >> >> <gre...@gm...> wrote: >> >>> Amir, >> >>> >> >>> We currently have 2 KMP projects to be aware of: >> >>> >> >>> "filesystems/ext4dev-snapshots" is the released version which normal >> >>> testers/people should be downloading from. We need to do our best to >> >>> keep it usable. >> >>> >> >>> "home:next4/ext4dev-snapshots" is the one that should only be used by >> >>> the next4 team. >> >>> >> >>> I just uploaded your new patch to there and will see if it builds. >> >>> (It was building last week with the old patch, but something happened >> >>> to factory recently and our KMP no longer builds. >> >> >> >> That's my bad. >> >> the patch ext4dev-trace.patch has an ugly ugly hack. >> >> it has the absolute path of the OBS BUILD directory hardcoded in the >> >> patch. >> >> I just could find another way to make the KMP build properly. >> >> Now OBS has changed the path from /usr/src/packages/BUILD >> >> to /home/abuild/rpmbuild/BUILD. >> >> I will try to fix that by fixing the hardcoded path. >> >> >> > >> > So now the module builds for Factory, but not for Thumbleweed, >> > which still builds under /usr/src/packages/BUILD :-( >> > I guess we can live with that problem for now... >> > >> > Amir. >> >> Tumbleweed will be moving on in the not too distant future to 3.2-rcx >> etc., so it is not a good target for us. >> >> Let's just worry about factory/12.1. 12.1 should stick with 3.1 for >> the next 18 months. >> >> Factory will move on two at some point, so 12.1 is our real target. >> OBS just doesn't have full 12.1 repo support yet. >> >> I'll try to test this build in the next day or so, then push it to the >> filesystem repo. >> >> Greg > > > > -- > Greg Freemyer > Head of EDD Tape Extraction and Processing team > Litigation Triage Solutions Specialist > http://www.linkedin.com/in/gregfreemyer > CNN/TruTV Aired Forensic Imaging Demo - > > http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/ > > The Norcross Group > The Intersection of Evidence & Technology > http://www.norcrossgroup.com > |
|
From: Greg F. <gre...@gm...> - 2011-11-02 15:26:18
|
Amir, I am now running kernel 3.1.0 with the ext4dev-kmp compiled from home:next4. I tried xfstests "./check -g auto" from Aditya's git repo. It failed on both test 113 and 255. That is on the first pass, so no snapshots were active. I "assume" that the official ext4 in 3.1.0 doesn't fail, but I haven't tested it. Greg On Mon, Oct 31, 2011 at 1:20 PM, Greg Freemyer <gre...@gm...>wrote: > On Mon, Oct 31, 2011 at 1:04 PM, Amir Goldstein <ami...@gm...> > wrote: > > On Mon, Oct 31, 2011 at 6:28 PM, Amir Goldstein <ami...@gm...> > wrote: > >> On Mon, Oct 31, 2011 at 6:03 PM, Greg Freemyer <gre...@gm...> > wrote: > >>> Amir, > >>> > >>> We currently have 2 KMP projects to be aware of: > >>> > >>> "filesystems/ext4dev-snapshots" is the released version which normal > >>> testers/people should be downloading from. We need to do our best to > >>> keep it usable. > >>> > >>> "home:next4/ext4dev-snapshots" is the one that should only be used by > >>> the next4 team. > >>> > >>> I just uploaded your new patch to there and will see if it builds. > >>> (It was building last week with the old patch, but something happened > >>> to factory recently and our KMP no longer builds. > >> > >> That's my bad. > >> the patch ext4dev-trace.patch has an ugly ugly hack. > >> it has the absolute path of the OBS BUILD directory hardcoded in the > patch. > >> I just could find another way to make the KMP build properly. > >> Now OBS has changed the path from /usr/src/packages/BUILD > >> to /home/abuild/rpmbuild/BUILD. > >> I will try to fix that by fixing the hardcoded path. > >> > > > > So now the module builds for Factory, but not for Thumbleweed, > > which still builds under /usr/src/packages/BUILD :-( > > I guess we can live with that problem for now... > > > > Amir. > > Tumbleweed will be moving on in the not too distant future to 3.2-rcx > etc., so it is not a good target for us. > > Let's just worry about factory/12.1. 12.1 should stick with 3.1 for > the next 18 months. > > Factory will move on two at some point, so 12.1 is our real target. > OBS just doesn't have full 12.1 repo support yet. > > I'll try to test this build in the next day or so, then push it to the > filesystem repo. > > Greg > -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer CNN/TruTV Aired Forensic Imaging Demo - http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/ The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com |
|
From: Greg F. <gre...@gm...> - 2011-11-01 21:47:19
|
Amir, Here's my mount options: /dev/sda3 on /xfstests_mnt type ext4dev (rw,relatime,user_xattr,acl,barrier=1,data=ordered) So I do have user_xattr set. I am not setting any mount options so all of the above must be default at least on openSUSE. Greg On Tue, Nov 1, 2011 at 4:30 AM, Amir G. <ami...@us...> wrote: > On Tue, Nov 1, 2011 at 6:22 AM, Greg Freemyer <gre...@gm...> wrote: >> Yongqiang, >> >> Below is not what I "meant" to do, but it is what I did: >> >> 1) Set the env variables for the test device and mount point. >> 2) Clear the env vars for the scratch device and mount point. >> 3) Using xfstests in its entirety from Aditya's repo: > > I saw many fixes in xfstests recently regarding fsstress, the util > which is used by test 070. > Not that I want to sweep a bug under the rug, but I wonder if the bug > also happens with latest xfstests. > >> 3.1) Run "./check -g auto" and let it finish >> 3.2) Run "./check 257" >> 3.3) While 257 is running, go to another console/terminal and cd into the >> test mount point >> 3.4) do a few "ls" and "du -s *" commands >> 3.5) leave PWD for the second console/terminal inside the mount point >> 3.6) allow 257 to complete. It failed because umount failed. >> 3.7) I somehow verified that 4 snapshots were still present as were some >> files/directories in my test fs. >> 3.8) Run "./check -g auto" again. It hung in test 070. > > From my experience, the hang bug only happens if user_xattr mount > option is enabled. > If I am not mistaken ext4 has changed the default of these options > recently to enabled. > > There are 2 bug fixes pending for kernel 3.2 which looks relevant: > c054fd6 ext4: fix race in xattr block allocation path > 6654361 ext4: use ext4_reserve_inode_write in ext4_xattr_set_handle > > Since I don't see any COW functions is the stack when test 070 hangs, > I suspect the bug may be an ext4 bug, but the snapshots increase the probability > of hitting it. > > Amir. > >> >> Greg >> >> On Mon, Oct 31, 2011 at 9:34 PM, Yongqiang Yang <xia...@gm...> >> wrote: >>> >>> Hi Amir and Greg, >>> >>> Could you give me explicit commands you used? That's ok on my system. >>> >>> >>> Yongqiang. >>> >>> On Tue, Nov 1, 2011 at 1:02 AM, Amir G. <ami...@us...> >>> wrote: >>> > On Mon, Oct 31, 2011 at 6:08 PM, Greg Freemyer <gre...@gm...> >>> > wrote: >>> >> Amir, >>> >> >>> >> I did not get ext4dev into the 12.1 official release. I don't know if >>> >> it would have been accepted. I got very busy on my real job and we >>> >> were already past the new submission stage as of early last week. >>> >> >>> >> I did upgrade my computer to 12.1 RC1 last week and tested ext4dev >>> >> with xfstests. >>> >> >>> >> On a clean filesystem with no snapshots, I was able to run a full >>> >> ./check -g auto. >>> >> >>> >> I then ran test 257 and it ran to completion. >>> >> >>> >> I then attempted to re-run the full suite with the now "agged" >>> >> filesystem and 4 snapshots in place. >>> >> >>> >> Test 070 never finished. (It has been running all weekend.) So we >>> >> definitely have a bug that needs to be addressed. >>> > >>> > Well, as I said, this bug is documented here: >>> > https://github.com/amir73il/ext4-snapshots/blob/ext4-snapshots/BUGS >>> > >>> > I hoped it went away, but never believed that it did ;-) >>> > >>> > Yongqiang, >>> > >>> > can you please check again if test 070 runs ok on your system. >>> > >>> > Thanks, >>> > Amir. >>> > >>> >> >>> >> Again, that was with kernel 3.1-rc9 >>> >> >>> >> Greg >>> >> -- >>> >> Greg Freemyer >>> >> Head of EDD Tape Extraction and Processing team >>> >> Litigation Triage Solutions Specialist >>> >> http://www.linkedin.com/in/gregfreemyer >>> >> CNN/TruTV Aired Forensic Imaging Demo - >>> >> >>> >> http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/ >>> >> >>> >> The Norcross Group >>> >> The Intersection of Evidence & Technology >>> >> http://www.norcrossgroup.com >>> >> >>> >> >>> >> ------------------------------------------------------------------------------ >>> >> Get your Android app more play: Bring it to the BlackBerry PlayBook >>> >> in minutes. BlackBerry App World™ now supports Android™ Apps >>> >> for the BlackBerry® PlayBook™. Discover just how easy and >>> >> simple >>> >> it is! http://p.sf.net/sfu/android-dev2dev >>> >> _______________________________________________ >>> >> Next3-devel mailing list >>> >> Nex...@li... >>> >> https://lists.sourceforge.net/lists/listinfo/next3-devel >>> >> >>> > >>> >>> >>> >>> -- >>> Best Wishes >>> Yongqiang Yang >> >> >> >> -- >> Greg Freemyer >> Head of EDD Tape Extraction and Processing team >> Litigation Triage Solutions Specialist >> http://www.linkedin.com/in/gregfreemyer >> CNN/TruTV Aired Forensic Imaging Demo - >> >> http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/ >> >> The Norcross Group >> The Intersection of Evidence & Technology >> http://www.norcrossgroup.com >> > -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer CNN/TruTV Aired Forensic Imaging Demo - http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/ The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com |
|
From: Amir G. <ami...@us...> - 2011-11-01 08:30:30
|
On Tue, Nov 1, 2011 at 6:22 AM, Greg Freemyer <gre...@gm...> wrote: > Yongqiang, > > Below is not what I "meant" to do, but it is what I did: > > 1) Set the env variables for the test device and mount point. > 2) Clear the env vars for the scratch device and mount point. > 3) Using xfstests in its entirety from Aditya's repo: I saw many fixes in xfstests recently regarding fsstress, the util which is used by test 070. Not that I want to sweep a bug under the rug, but I wonder if the bug also happens with latest xfstests. > 3.1) Run "./check -g auto" and let it finish > 3.2) Run "./check 257" > 3.3) While 257 is running, go to another console/terminal and cd into the > test mount point > 3.4) do a few "ls" and "du -s *" commands > 3.5) leave PWD for the second console/terminal inside the mount point > 3.6) allow 257 to complete. It failed because umount failed. > 3.7) I somehow verified that 4 snapshots were still present as were some > files/directories in my test fs. > 3.8) Run "./check -g auto" again. It hung in test 070. >From my experience, the hang bug only happens if user_xattr mount option is enabled. If I am not mistaken ext4 has changed the default of these options recently to enabled. There are 2 bug fixes pending for kernel 3.2 which looks relevant: c054fd6 ext4: fix race in xattr block allocation path 6654361 ext4: use ext4_reserve_inode_write in ext4_xattr_set_handle Since I don't see any COW functions is the stack when test 070 hangs, I suspect the bug may be an ext4 bug, but the snapshots increase the probability of hitting it. Amir. > > Greg > > On Mon, Oct 31, 2011 at 9:34 PM, Yongqiang Yang <xia...@gm...> > wrote: >> >> Hi Amir and Greg, >> >> Could you give me explicit commands you used? That's ok on my system. >> >> >> Yongqiang. >> >> On Tue, Nov 1, 2011 at 1:02 AM, Amir G. <ami...@us...> >> wrote: >> > On Mon, Oct 31, 2011 at 6:08 PM, Greg Freemyer <gre...@gm...> >> > wrote: >> >> Amir, >> >> >> >> I did not get ext4dev into the 12.1 official release. I don't know if >> >> it would have been accepted. I got very busy on my real job and we >> >> were already past the new submission stage as of early last week. >> >> >> >> I did upgrade my computer to 12.1 RC1 last week and tested ext4dev >> >> with xfstests. >> >> >> >> On a clean filesystem with no snapshots, I was able to run a full >> >> ./check -g auto. >> >> >> >> I then ran test 257 and it ran to completion. >> >> >> >> I then attempted to re-run the full suite with the now "agged" >> >> filesystem and 4 snapshots in place. >> >> >> >> Test 070 never finished. (It has been running all weekend.) So we >> >> definitely have a bug that needs to be addressed. >> > >> > Well, as I said, this bug is documented here: >> > https://github.com/amir73il/ext4-snapshots/blob/ext4-snapshots/BUGS >> > >> > I hoped it went away, but never believed that it did ;-) >> > >> > Yongqiang, >> > >> > can you please check again if test 070 runs ok on your system. >> > >> > Thanks, >> > Amir. >> > >> >> >> >> Again, that was with kernel 3.1-rc9 >> >> >> >> Greg >> >> -- >> >> Greg Freemyer >> >> Head of EDD Tape Extraction and Processing team >> >> Litigation Triage Solutions Specialist >> >> http://www.linkedin.com/in/gregfreemyer >> >> CNN/TruTV Aired Forensic Imaging Demo - >> >> >> >> http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/ >> >> >> >> The Norcross Group >> >> The Intersection of Evidence & Technology >> >> http://www.norcrossgroup.com >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> Get your Android app more play: Bring it to the BlackBerry PlayBook >> >> in minutes. BlackBerry App World™ now supports Android™ Apps >> >> for the BlackBerry® PlayBook™. Discover just how easy and >> >> simple >> >> it is! http://p.sf.net/sfu/android-dev2dev >> >> _______________________________________________ >> >> Next3-devel mailing list >> >> Nex...@li... >> >> https://lists.sourceforge.net/lists/listinfo/next3-devel >> >> >> > >> >> >> >> -- >> Best Wishes >> Yongqiang Yang > > > > -- > Greg Freemyer > Head of EDD Tape Extraction and Processing team > Litigation Triage Solutions Specialist > http://www.linkedin.com/in/gregfreemyer > CNN/TruTV Aired Forensic Imaging Demo - > > http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/ > > The Norcross Group > The Intersection of Evidence & Technology > http://www.norcrossgroup.com > |
|
From: Greg F. <gre...@gm...> - 2011-11-01 04:22:43
|
Yongqiang, Below is not what I "meant" to do, but it is what I did: 1) Set the env variables for the test device and mount point. 2) Clear the env vars for the scratch device and mount point. 3) Using xfstests in its entirety from Aditya's repo: 3.1) Run "./check -g auto" and let it finish 3.2) Run "./check 257" 3.3) While 257 is running, go to another console/terminal and cd into the test mount point 3.4) do a few "ls" and "du -s *" commands 3.5) leave PWD for the second console/terminal inside the mount point 3.6) allow 257 to complete. It failed because umount failed. 3.7) I somehow verified that 4 snapshots were still present as were some files/directories in my test fs. 3.8) Run "./check -g auto" again. It hung in test 070. Greg On Mon, Oct 31, 2011 at 9:34 PM, Yongqiang Yang <xia...@gm...>wrote: > Hi Amir and Greg, > > Could you give me explicit commands you used? That's ok on my system. > > > Yongqiang. > > On Tue, Nov 1, 2011 at 1:02 AM, Amir G. <ami...@us...> > wrote: > > On Mon, Oct 31, 2011 at 6:08 PM, Greg Freemyer <gre...@gm...> > wrote: > >> Amir, > >> > >> I did not get ext4dev into the 12.1 official release. I don't know if > >> it would have been accepted. I got very busy on my real job and we > >> were already past the new submission stage as of early last week. > >> > >> I did upgrade my computer to 12.1 RC1 last week and tested ext4dev > >> with xfstests. > >> > >> On a clean filesystem with no snapshots, I was able to run a full > >> ./check -g auto. > >> > >> I then ran test 257 and it ran to completion. > >> > >> I then attempted to re-run the full suite with the now "agged" > >> filesystem and 4 snapshots in place. > >> > >> Test 070 never finished. (It has been running all weekend.) So we > >> definitely have a bug that needs to be addressed. > > > > Well, as I said, this bug is documented here: > > https://github.com/amir73il/ext4-snapshots/blob/ext4-snapshots/BUGS > > > > I hoped it went away, but never believed that it did ;-) > > > > Yongqiang, > > > > can you please check again if test 070 runs ok on your system. > > > > Thanks, > > Amir. > > > >> > >> Again, that was with kernel 3.1-rc9 > >> > >> Greg > >> -- > >> Greg Freemyer > >> Head of EDD Tape Extraction and Processing team > >> Litigation Triage Solutions Specialist > >> http://www.linkedin.com/in/gregfreemyer > >> CNN/TruTV Aired Forensic Imaging Demo - > >> > http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/ > >> > >> The Norcross Group > >> The Intersection of Evidence & Technology > >> http://www.norcrossgroup.com > >> > >> > ------------------------------------------------------------------------------ > >> Get your Android app more play: Bring it to the BlackBerry PlayBook > >> in minutes. BlackBerry App World™ now supports Android™ Apps > >> for the BlackBerry® PlayBook™. Discover just how easy and > simple > >> it is! http://p.sf.net/sfu/android-dev2dev > >> _______________________________________________ > >> Next3-devel mailing list > >> Nex...@li... > >> https://lists.sourceforge.net/lists/listinfo/next3-devel > >> > > > > > > -- > Best Wishes > Yongqiang Yang > -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer CNN/TruTV Aired Forensic Imaging Demo - http://insession.blogs.cnn.com/2010/03/23/how-computer-evidence-gets-retrieved/ The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com |
