This is because HugePages_rsvd is essentially read from HugePages_Free. Meaning, out of 596 huge pages which are free, 594 are already reserved by some application for use. That is kernel has committed that those 594 huge pages are available for the application.
If there is a request for 3 huge pages now, then it will fail as only 2 are available to be reserved. Think of it as a malloc() call, when you reserve memory virtual pages to account for the VSZ for the process but when the process actually uses them, it becomes the RSZ (running set) of the process.
As huge pages are always resident on main memory, when an app requests them kernel decrements it from free pool and increase the Rsvd counter.
This is from the kernel source.
38HugePages_Total is the size of the pool of huge pages.
39HugePages_Free is the number of huge pages in the pool that are not yet
41HugePages_Rsvd is short for "reserved," and is the number of huge pages for
42 which a commitment to allocate from the pool has been made,
43 but no allocation has yet been made. Reserved huge pages
44 guarantee that an application will be able to allocate a
45 huge page from the pool of huge pages at fault time.
46HugePages_Surp is short for "surplus," and is the number of huge pages in
47 the pool above the value in /proc/sys/vm/nr_hugepages. The
48 maximum number of surplus huge pages is controlled by