Hi all,
Does anyone know what the bug number that is fixed in OnTap 7.3.x so
that CommVault 7.x will work properly with stubs to restore files
which have been moved off to secondary storage?
We're currently running 7.2.6.1 and 7.2.6.1P8 on our filers, and I
just want to see if I can figure out which fpolicy (my assumption) bug
was fixed.
As I understand it, the bug was that on the first access, the file
wasn't restored, but on the second it was. This could lead to
problems if users found …
[View More]the stubs and either edited them or worse,
thought their data was hosed.
Of course, moving to 7.3.1.1 won't be too hard, but with all the new
iSCSI Luns we've been adding, it makes upgrades harder than when we
were just NFS/CIFS exports. Reboots are much simpler then. *grin*
THanks,
John
John Stoffel - Senior Staff Systems Administrator - System LSI Group
Toshiba America Electronic Components, Inc. - http://www.toshiba.com/taec
john.stoffel(a)taec.toshiba.com - 508-486-1087
[View Less]
On Fri, 2 Oct 2009, Jeff Mohler wrote:
> Qtree stats are ONLY reads and writes.
>
> No metadata ops (readdir, etc, etc, etc...wafl IO..etc..etc.etc..even
> CIFS has gobs of metadata ops, just like NFS)
Jeff, we were thinking similarly as well...
I compared the output of the three following stats, 60 seconds apart,
and clearly the qtree stats is the smallest of the three:
qtree stats 972297
cifs stat 2396439
uptime 2395260
However, given our workload,…
[View More] we have tons of CIFS getattrs, and a small
fraction of reads or writes. So, I think our suspicions are true (not
all ops are reported by qtree stats) but the specific excluded ops in
our case seem to still be off.
Hrmph.
Until next time...
The MathWorks, Inc. 508-647-7000 x7792
3 Apple Hill Drive, Natick, MA 01760-2098 508-647-7001 FAX
tmerrill(a)mathworks.com http://www.mathworks.com
---
[View Less]
Metadata work, mostly - directory crawls, access checks, things like that (in CIFS). In NFS, ACCESS, READDIR, READDIR+ , stuff like that.
I think you can use 'cifs top -s ops' to see the busiest clients hitting the system. If the ones at the top have very high ops, but not many reads/writes, those could be your guys.
That said, it's all about latency. If it isn't driving latency higher, shouldn't be a concern. Those are different stats commands, though, can't remember right now......
…
[View More]--- On Fri, 6/5/09, Page, Jeremy <jeremy.page(a)gilbarco.com> wrote:
> From: Page, Jeremy <jeremy.page(a)gilbarco.com>
> Subject: Other OPS?
> To: toasters(a)mathworks.com
> Date: Friday, June 5, 2009, 3:10 PM
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> What
> causes other ops?
> I understand that pretty much everything that hits the
> filer requires something
> but I am seeing what looks like a very high number of other
> ops when I do a
> stats show. Does this indicate a problem or is it just a
> busy box? It’s
> a mixed mode volume. Just trying to figure out what’s
> causing it to work
> so hard.
>
>
>
>
>
> Instance
> total_ops read_ops write_ops other_ops nfs_read_ops
> nfs_write_op nfs_other_op
> cifs_read_op cifs_write_o cifs_other_o
>
>
> /s
> /s
> /s
> /s
> /s
> /s
> /s
> /s
> /s
> /s
>
>
> shares
> 1633
> 984
> 139
> 509
> 0
> 1
> 34
> 984
> 137
> 473
>
>
> shares
> 2085
> 1173
> 257
> 654
> 0
> 2
> 18
> 1173
> 255
> 634
>
>
> shares
> 2593
> 1483
> 253
> 856
> 0
> 2
> 221
> 1483
> 251
> 634
>
>
> shares
> 3268
> 2306
> 170
> 791
> 0
> 1
> 222
> 2305
> 168
> 569
>
>
>
>
>
>
>
>
>
>
>
> Please be advised that this email may contain confidential
> information.
>
> If you are not the intended recipient, please do not read,
> copy or
>
> re-transmit this email. If you have received this email in
> error,
>
> please notify us by email by replying to the sender and by
> telephone
>
> (call us collect at +1 202-828-0850) and delete this
> message and any
>
> attachments. Thank you in advance for your cooperation and
> assistance.
>
>
>
> In addition, Danaher and its subsidiaries disclaim that the
> content of
>
> this email constitutes an offer to enter into, or the
> acceptance of,
>
> any
>
> contract or agreement or any amendment thereto; provided
> that the
>
> foregoing disclaimer does not invalidate the binding effect
> of any
>
> digital or other electronic reproduction of a manual
> signature that is
>
> included in any attachment to this email.
>
>
[View Less]
Hi All
Does anyone know about CIFS Standard Pool, recently we got a message on the filer that CIFS Standard pool was full and new requests could not be handled etc???
Thanx
Xishan
Hey Toasters,
We're experiencing problems in our Snapmanager environment:
Since our eMail team changed the mailrelay hosts, we are not able to send emails with Snapmanager applications anymore.
We tracked the problem down to the root cause and found that Snapmanger doesn't use the FQDN in the SMTP Helo cmd to connect to the email relay.
According to RFC 821 (SMTP Protocol) the FQDN has to be submitted otherwise the mail relay "normally" does not accept the message (some mail relays do, some …
[View More]don't and ours doesn't accept it).
Did anybody run into the same issue before?
Is there any known solution or workaround for this problem, without installing any additional apps on windows ?
Cheers
Andreas
--
WINCOR NIXDORF International GmbH
Sitz der Gesellschaft: Paderborn
Registergericht Paderborn HRB 3507
Gesch�ftsf�hrer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. J�rgen Wunram
Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller
Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193
Diese E-Mail enth�lt vertrauliche Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt�mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.
This e-mail may contain confidential information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
[View Less]