Another typical case when I would recommend placing multiple LUNs on the same volume is to get "crash consistent" snapshot of these LUNs. E.g. for all LUNs belonging to the same server or hosting parts of the same database. ... View more

The title says "FAS270". There is no way to run 8.1 on FAS270, so whether or not FAS270 removed FilerView is irrelevant. ... View more

Hmm … and if ports are used for shelves and not for FCP? ... View more

After some research - in 8.x ports below 1024 are blocked by explicit firewall rule in low level FreeBSD. These rules are part of read-only root image, so there is no way to change them. Looks like deliberate decision; so the only way to change it (at least, to make it configurable) is to raise issue with NetApp. ... View more

Documentation describes “The SnapLock for SnapVault feature—secure SnapVault destination” so it is apparently supported. Also, if your customer is using SnapLock Enterprise, it is possible to destroy snaplock volume. ... View more

Yes, your default route goes via e0M. There is no reason to have e0M if it is on the same network as another interface. Any interface can be used for management. ... View more

sdX will depend on order in which devices are seen by Linux host. You can make no assumptions about sdX names. They are just internal kernel handles, the only requirement is they are unique at any given time. The names under /dev/disk/by-* will remain the same, but may point to different sdX after reboot. ... View more

Who talks about “without adding disks”? ☺ “live upgrade the 32bit aggrs to 64bit (> 16Tb)” ... View more

Most likely because in one case it is using Keberos and in another case - NTLM. Does this kb help? https://kb.netapp.com/support/index?page=content&id=2013374 Notice, that is just workaround, not a solution. It is better to investigate why accessing alias falls back to NTLM and fix the root cause. Do you have the same alias defined in DNS? Another consideration - this is indication of some service on host accessing files on filer. Is it really intentional? From security and auditing PoV it would be better to run service under named account in this case; this would allow you to set ACLs and audit access. Message was edited by: Andrey Borzenkov ... View more

Normally resized LUN should be recognized immediately if whole device is used (e.g., as LVM PV). Are you using partition on this LUN? ... View more

For a start, 8.x is not supported by FAS3020 ... ... View more

From this thread though, it looks like things doesn't always work like described in Config E above. Bur OP did not have Config E; lun space reservation was enabled as can be seen in FR kicking in. With LUN space reservation off no FR is ever allocated and its value is irrelevant. ... View more

Are you sure about this? Now no more It does require more temporary space during extended period of time though ... simsim*> df tv Filesystem              kbytes       used      avail capacity  Mounted on /vol/tv/                 20480      15080       5400      74%  /vol/tv/ bor@opensuse:~> sudo dd if=/dev/urandom of=/dev/sdb1 bs=1M  oflag=direct count=4 4+0 records in 4+0 records out 4194304 bytes (4.2 MB) copied, 3.46915 s, 1.2 MB/s simsim*> df tv Filesystem              kbytes       used      avail capacity  Mounted on /vol/tv/                 20480      16692       3788      82%  /vol/tv/ simsim*> df tv Filesystem              kbytes       used      avail capacity  Mounted on /vol/tv/                 20480      19200       1280      94%  /vol/tv/ simsim*> df tv Filesystem              kbytes       used      avail capacity  Mounted on /vol/tv/                 20480      15080       5400      74%  /vol/tv/ And if you are unlucky enough ... bor@opensuse:~> sudo dd if=/dev/urandom of=/dev/sdb1 bs=1M  oflag=direct count=6 dd: writing `/dev/sdb1': Input/output error 6+0 records in 5+0 records out 5242880 bytes (5.2 MB) copied, 6.95034 s, 754 kB/s simsim*> Tue May  1 13:00:54 MSK [simsim:wafl.vol.full:notice]: file system on volume tv is full Tue May  1 13:00:54 MSK [simsim:scsitarget.lun.noSpace:error]: LUN '/vol/tv/lv' has run out of space. Tue May  1 13:00:55 MSK [simsim:lun.offline:warning]: LUN /vol/tv/lv has been taken offline simsim*> df tv Filesystem              kbytes       used      avail capacity  Mounted on /vol/tv/                 20480      15144       5336      74%  /vol/tv/ simsim*> lun show /vol/tv/lv         /vol/tv/lv                    15m (15728640)      (r/w, offline, mapped) I do not know how long it takes to release overwritten blocks, but it seems to take significantly more time than in normal case. ... View more

gets extracted during first boot (mroot and pmroot/pmroot_late). A word of caution. It appears that some settings are not migrated during this process. So timezone was reset, sshd key changed, diag user got locked again and possibly something else I did not yet notice. So this procedure is indeed quite dangerous on real system as effects are unpredictable. ... View more

But I think it is a waste of space *if* dedupe ratio is low Sure. FR is a waste of space. This is simply the question of more or less safe defaults. I prefer what NetApp does - make sure it is safe by default and if user wants to shoot himself in the foot - the gun is there. but if there is no snapshots OK, I apologize - I let myself to be misled by your comments and so my answer was misleading as well. The actual problem has nothing to do with snapshots nor with deduplication ratio. Please accept the simple fact - blocks that had been processed by deduplication scan are frozen until next scan. This means that if you have "1TB LUN, de-dupe enabled (& run) with no savings" - 1TB of your space is frozen for unknown amount of time. So you need space for future writes. Default is conservative 100%. It is not related to whether you are going to take any snapshot. Nor is it related to how good future data may be deduplicated, because they must be stored in "fat" form initially. Nor is it related to how low existing deduplication ratio is, because space is already gone. ... View more

Well ... without diagnostic at the time of problem it makes little sense to speculate. There is no way to take in account deduplication ratio for simple reason - you cannot predict future. Even if existing data are all compressed into single block, new data could be all different. So you need to ensure as much space to accomodate it. If you know your data - adjust FR; this has always been the case Ayone knows if it is possible to see how much of FR is in use? ... View more

Seems to work (8.1RC3 => 8.1). One must be careful to record serial and sysid and adjust before first boot, as they are different in new image. Otherwise no "software install" seems necessary - looking at DOT archive content it contains only CF stuff which gets extracted during first boot (mroot and pmroot/pmroot_late). Now I wonder how one can update VMware tools ... View more

7.x was updated by installing new version and updating root volume without download. I wonder if it's possible to just replace DataONTAP-cf.vmdk (which should contain the binaries). This should have the same effect as reimaging boot device on real system? ... View more

Any news on it? Simulator 7.x was actually upgradeable. Pity 8.x lost this ... ... View more

Funnily enough, FR was designed to prevent LUNs from going offline Well, OP did never mention LUN going offline. I did experiment with A-SIS and LUN and I can claim with confidence that in the state shown there is enough space for write to LUN even though NetApp will loudly complain that volume is 100% full. I still am not sure what exact problem there was. FR looks more like red herring here. FR kicked in with no snapshots in the volume, but with dedupe enabled - I vaguely remember there is hidden snapshot, or something like that to be blamed. Yes. Volume with A-SIS behaves exactly like volume with snapshots w.r.t LUN.The practical problem is - deduplication is post-process. And we have to make sure there is enough space to overwrite what had already been written which goes into new blocks until sis job runs next time. Even if it had been deduplicated. So we need to reserve amount of space equal - surprise - to logical amount of space LUN consumed so far. Unfortunately, existing tools do not present clear breakdown of space consumption. E.g. with space reserved LUNs (default) "df -s" simply lies. It computes space savings against "used" column of df - which in case of space reservation is reserved, not consumed space. Here is an example: simsim> df -r v1 Filesystem              kbytes       used      avail   reserved  Mounted on /vol/v1/                 20480      15828       4652    (14412) /vol/v1/ simsim> df -s v1 Filesystem                used      saved       %saved /vol/v1/                 15828      14328          48% simsim> lun set reservation /vol/v1/lv disable simsim> df -r v1 Filesystem              kbytes       used      avail   reserved  Mounted on /vol/v1/                 20480        396      20084          0  /vol/v1/ simsim> df -s v1 Filesystem                used      saved       %saved /vol/v1/                   396      14328          97% As soon as we step into thin provisioning territory, everything becomes very confusing ... ... View more

NEVER do giveback without having console connection open, preferably to both controllers, but at least to the taken over controller. I have learned it the hard way … For that matter never perform anything that requires controller reboot without having console. Fortunately, with modern hardware this is not the issue anymore (although sometimes it is hard to persuade customers to connect RLM) and does not require long trip to datacenter. ... View more

Yes, I would love to understand what actually was going on here. Unfortunately, there is not enough information (for a start, we do not even know whether there was anything else on this volume) nor do we know the history of events. ... View more