Re: [zfs-discuss] grrr, How to get rid of mis-touched file named `-c'
On 11/26/2011 5:30 AM, Brandon High wrote: On Wed, Nov 23, 2011 at 11:43 AM, Harry Putnamrea...@newsguy.com wrote: OK, I'm out of escapes. or other tricks... other than using emacs but I haven't installed emacs as yet. I can just ignore them of course, until such time as I do get emacs installed, but by now I just want to know how it might be done from a shell prompt. rm ./-c ./-O ./-k And many versions of getopt support the use of -- as the end of options indicator so that you can do rm -- -c -O -k to remove those as well. Gregg Wonderly ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Confusing zfs error message
2011-11-27 5:24, Ian Collins пишет: I was trying to destroy a filesystem and I was baffled by the following error: zfs destroy -r rpool/test/opt cannot destroy 'rpool/test/opt/csw@2001_1405': dataset already exists zfs destroy -r rpool/test/opt/csw@2001_1405 cannot destroy 'rpool/test/opt/csw@2001_1405': snapshot is cloned It turns out there was a zfs receive writing to the filesystem. A more sensible error would have been dataset is busy. I would not be surprised if zfs recv would receive an incremental stream doing work like this: * clone the currently available origin snapshot into a temporary dataset * write new data into this dataset (i.e. if the receive fails, older FS remains consistent) * promote the temp dataset after a sucessful receive This is a wild guess without consulting the sources, but sounds reasonable due to practice. If so, the error message as is happens to be valid. But you're correct that it might be more informative for this corner case as well... :) //Jim ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] grrr, How to get rid of mis-touched file named `-c'
Did you try rm -- filename ? Sent from my iPhone On Nov 23, 2011, at 1:43 PM, Harry Putnam rea...@newsguy.com wrote: Somehow I touched some rather peculiar file names in ~. Experimenting with something I've now forgotten I guess. Anyway I now have 3 zero length files with names -O, -c, -k. I've tried as many styles of escaping as I could come up with but all are rejected like this: rm \-c rm: illegal option -- c usage: rm [-fiRr] file ... Ditto for: [\-]c '-c' *c '-'c \075c OK, I'm out of escapes. or other tricks... other than using emacs but I haven't installed emacs as yet. I can just ignore them of course, until such time as I do get emacs installed, but by now I just want to know how it might be done from a shell prompt. ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] grrr, How to get rid of mis-touched file named `-c'
You could list by inode, then use find with rm. # ls -i 7223 -O # find . -inum 7223 -exec rm {} \; David On 11/23/11 2:00 PM, Jason King (Gmail) jason.brian.k...@gmail.com wrote: Did you try rm -- filename ? Sent from my iPhone On Nov 23, 2011, at 1:43 PM, Harry Putnam rea...@newsguy.com wrote: Somehow I touched some rather peculiar file names in ~. Experimenting with something I've now forgotten I guess. Anyway I now have 3 zero length files with names -O, -c, -k. I've tried as many styles of escaping as I could come up with but all are rejected like this: rm \-c rm: illegal option -- c usage: rm [-fiRr] file ... Ditto for: [\-]c '-c' *c '-'c \075c OK, I'm out of escapes. or other tricks... other than using emacs but I haven't installed emacs as yet. I can just ignore them of course, until such time as I do get emacs installed, but by now I just want to know how it might be done from a shell prompt. ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] grrr, How to get rid of mis-touched file named `-c'
On Mon, Nov 28, 2011 at 11:28 AM, Smith, David W. smith...@llnl.gov wrote: You could list by inode, then use find with rm. # ls -i 7223 -O # find . -inum 7223 -exec rm {} \; This is the one solution I'd recommend against, since it would remove hardlinks that you might care about. Also, this thread is getting long, repetitive, tiring. Please stop. This is a standard issue Unix beginner question, just like my test program does nothing. Nico -- ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Re: [zfs-discuss] Compression
After additional digging and investigation, looks like it's showing me the compressed size, which is good. I've regroomed the storage pools and started moving things back, and I'm seeing files deflate back to their expected size. What really tipped me off was when I decided to log in to one of the VM's. VMware showed 120GB provisioned, 92GB allocated on the standard block storage. After storage vmotioning back to NFS, it showed 62GB allocated. The key was when I logged in to the machine, Windows said it was using 90GB. All said and done, it was a good adventure, and I got the info that I needed. Thanks to all that took the time to reply. -Matt Breitbach -Original Message- From: Donal Farrell [mailto:vmlinuz...@gmail.com] Sent: Wednesday, November 23, 2011 10:42 AM To: Matt Breitbach Subject: Re: [zfs-discuss] Compression is this on esx 3.5.x? or 4.x or greater? The reason i ask is that svmotion to and from nfs datastores did not work correctly in esx 3.5.x Also can you past the output of cat /vmfs/volumes/datastore/vmname.vmdk here? On Wed, Nov 23, 2011 at 1:55 PM, Matt Breitbach matth...@flash.shanje.com wrote: Currently using NFS to access the datastore. -Matt -Original Message- From: Richard Elling [mailto:richard.ell...@gmail.com] Sent: Tuesday, November 22, 2011 11:10 PM To: Matt Breitbach Cc: zfs-discuss@opensolaris.org Subject: Re: [zfs-discuss] Compression Hi Matt, On Nov 22, 2011, at 7:39 PM, Matt Breitbach wrote: So I'm looking at files on my ZFS volume that are compressed, and I'm wondering to myself, self, are the values shown here the size on disk, or are they the pre-compressed values. Google gives me no great results on the first few pages, so I headed here. This really relates to my VMware environment. I had some things happen on my platform that required me to Storage Vmotion everything off of a particular zpool. When I did that, I saw most VM's inflate to nearly their thick provisioned size. What didn't swell to that size went to about 2/3 provisioned (non-Nexenta storage). I have been seeing 1.3-1.5x compression ratios on pretty much everything I turn compression on for (these are general use VM's - webservers,SQL,firewall,etc). My question is this - when I'm looking in the file structure, or in the datastore browser in VMware, am I seeing the uncompressed file size, or the compressed filesize? My gut tells me that since they inflated _so_ badly when I storage vmotioned them, that they are the compressed values, but I would love to know for sure. How are you measuring the space? Are you using block (iscsi/fc) or NFS to access the datastores from ESXi? -- richard -- ZFS and performance consulting http://www.RichardElling.com LISA '11, Boston, MA, December 4-9 ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss ___ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss