UNSOLVED

jkuhn1

updated

19 years ago

J

jkuhn1

34 Posts

0

531

November 13th, 2007 07:00

networker 7.3.3 mminfo reporting volume full when it isn't - diskbackup

$ mminfo -m
SIUMED.001 213 GB 100% 12/13/2007 2 KB 1 0 KB
SIUMED.002 538 GB full 12/10/2007 2323 MB 0 0 KB
SIUMED.003 486 GB full 12/11/2007 1339 MB 0 0 KB
SIUMED.004 462 GB full 12/07/2007 6544 KB 0 0 KB
SIUMED.005 8407 MB full 11/09/2007 2491 MB 0 0 KB
SIUMED.006 275 GB full 11/19/2007 332 MB 0 0 KB

$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 1.1T 522G 511G 51% /nsrdata/1
/dev/sda2 1.1T 1.1T 0 100% /nsrdata/2
/dev/sda3 1.1T 1.1T 0 100% /nsrdata/3
/dev/sdb1 1.1T 1.1T 0 100% /nsrdata/4
/dev/sdb2 1.1T 54G 979G 6% /nsrdata/5
/dev/sdb3 1.1T 437G 596G 43% /nsrdata/6

Red Hat Linux AS 4
NetWorker version 7.3 SP3.Build.510

Any ideas?
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    200

    0

    Posted November 13th, 2007 13:00

    2 possible causes:
    - there was some sort of I/O error which led device to be marked full (should be visible from logs)
    - nsrim did not put device back into appendable state (should be visible from logs)

    Second one is known issue and if that would be your problem you will need to obtain patch from your support.
  • jkuhn1

    34 Posts

    200

    0

    Posted January 7th, 2008 08:00

    Where can find more information on the nsrim known issue? I didn't find anything in 7.3.3 release notes. I don't find anything in the log about the device changing status. Support suggested a default volume capacity and suggested I use advanced file type instead of file type. I prefer a file type device. I have re-labeled the device with a volume capacity defined. I see space recovered from the device, but nothing written to it with on ly 1 other writable device available. Any ideas?

    mminfo -m
    SIUMED.006 363 GB full 01/19/2008 8171 KB 4 1024 GB

    df -h
    /dev/sdb3 1.1T 842G 191G 82% /nsrdata/6

    12/25/07 01:10:00 nsrd: media info: Recovered 525 MB by deleting 4 savesets from device /nsrdata/6.
    12/26/07 01:03:40 nsrd: media info: Recovered 386 MB by deleting 6 savesets from device /nsrdata/6.
    12/27/07 01:59:48 nsrd: media info: Recovered 1708 MB by deleting 12 savesets from device /nsrdata/6.
    12/29/07 03:08:19 nsrd: media info: Recovered 27 GB by deleting 23 savesets from device /nsrdata/6.
    12/31/07 00:05:06 nsrd: media info: Recovered 11 GB by deleting 52 savesets from device /nsrdata/6.
    01/01/08 01:10:34 nsrd: media info: Recovered 77 MB by deleting 3 savesets from device /nsrdata/6.
    01/02/08 01:08:51 nsrd: media info: Recovered 1168 MB by deleting 5 savesets from device /nsrdata/6.
    01/03/08 01:56:43 nsrd: media info: Recovered 623 MB by deleting 8 savesets from device /nsrdata/6.
    01/05/08 02:58:10 nsrd: media info: Recovered 72 GB by deleting 133 savesets from device /nsrdata/6.
    01/06/08 02:17:15 nsrd: media info: Recovered 140 GB by deleting 149 savesets from device /nsrdata/6.
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    200

    0

    Posted January 27th, 2008 11:00

    Usually you find those via support.

    With file device capacity defined will be used to determine max size of device. In your case that does not appear to be the problem. Have you checked log to see when device was marked full and if something strange has happened around that time?

    I still suspect the issue I said before as that issue was known with file devices (exactly what you have). It is already fixed in 7.4.1.