I updated to Sol10u3 last night, and I''m still seeing different differences between "du -h" and "ls -h". "du" seems to take into account raidz and compression -- if this is correct, please let me know. It makes sense that "du" reports actual disk usage, but this makes some scripts I wrote very broken (need real sizes of files in a directory to be able to put them on dvd isos). Sol10u3 on 3 disk RaidZ: [splus at solaris:~/burnout/2006-11-30]$ ls -lh JMS-data-1-2006-11-30.iso -rw-r--r-- 1 splus splus 3.5G Dec 1 10:15 JMS-data-1-2006-11-30.iso [splus at solaris:~/burnout/2006-11-30]$ du -hs JMS-data-1-2006-11-30.iso 5.2G JMS-data-1-2006-11-30.iso Thanks, Jeb This message posted from opensolaris.org
Hello Jeb,
Tuesday, December 12, 2006, 6:04:36 PM, you wrote:
JC> I updated to Sol10u3 last night, and I''m still seeing different
JC> differences between "du -h" and "ls -h".
JC> "du" seems to take into account raidz and compression -- if
this is correct, please let me know.
JC> It makes sense that "du" reports actual disk usage, but this
JC> makes some scripts I wrote very broken (need real sizes of files
JC> in a directory to be able to put them on dvd isos).
JC> Sol10u3 on 3 disk RaidZ:
JC> [splus at solaris:~/burnout/2006-11-30]$ ls -lh JMS-data-1-2006-11-30.iso
JC> -rw-r--r-- 1 splus splus 3.5G Dec 1 10:15 JMS-data-1-2006-11-30.iso
JC> [splus at solaris:~/burnout/2006-11-30]$ du -hs JMS-data-1-2006-11-30.iso
JC> 5.2G JMS-data-1-2006-11-30.iso
After upgrade you did actually re-create your raid-z pool, right?
--
Best regards,
Robert mailto:rmilkowski at task.gda.pl
http://milek.blogspot.com
> After upgrade you did actually re-create your raid-z > pool, right?No, but I did "zpool upgrade -a". Hmm, I guess I''ll try re-writing the data first. I know you have to do that if you change compression options. Ok -- rewriting the data doesn''t work ... I''ll create a new temp pool and see what that does ... then I''ll investigate options for recreating my big pool ... Thanks for the info, Jeb This message posted from opensolaris.org
Hello Jeb, Tuesday, December 12, 2006, 7:11:30 PM, you wrote:>> After upgrade you did actually re-create your raid-z >> pool, right?JC> No, but I did "zpool upgrade -a". JC> Hmm, I guess I''ll try re-writing the data first. I know you have JC> to do that if you change compression options. IIRC you have to re-create entire raid-z pool to get it fixed - just rewriting data or upgrading a pool won''t do it. -- Best regards, Robert mailto:rmilkowski at task.gda.pl http://milek.blogspot.com
Jeb Campbell wrote:>> After upgrade you did actually re-create your raid-z >> pool, right? > > No, but I did "zpool upgrade -a". > > Hmm, I guess I''ll try re-writing the data first. I know you have to do that if you change compression options. > > Ok -- rewriting the data doesn''t work ... > > I''ll create a new temp pool and see what that does ... then I''ll investigate options for recreating my big pool ...Unfortunately, this bug is only fixed when you create the pool on the new bits. --matt
> IIRC you have to re-create entire raid-z pool to get > it fixed - just > rewriting data or upgrading a pool won''t do it.You are correct ... Now I have to find some place to stick +1TB of temp files ;) Thanks for the help, Jeb This message posted from opensolaris.org
Is there an easy way to determine whether a pool has this fix applied or not? This message posted from opensolaris.org
Robert Milkowski
2006-Dec-12 22:30 UTC
[zfs-discuss] Re: Re: Sol10u3 -- is "du" bug fixed?
Hello Anton,
Tuesday, December 12, 2006, 9:36:41 PM, you wrote:
ABR> Is there an easy way to determine whether a pool has this fix applied or
not?
Yep.
Just do ''df -h'' and see what is a reported size of a pool. It
should
be something like N-1 times disk size for each raid-z group. If it is
N times disk size then it was created before fix.
--
Best regards,
Robert mailto:rmilkowski at task.gda.pl
http://milek.blogspot.com