Skip to main content
Start a Conversation

Unsolved

jer0nim01

1 Rookie

 • 

15 Posts

46

February 11th, 2025 13:40

aftd status

Is this normal?

# mminfo -q volume=backups.003 -avot6095:mminfo: no matches found for the query

mminfo -mbackups.003            31 GB 100%  04/01/25 2230 GB    82      0 KB

# df -h .Filesystem                         Size  Used Avail Use% Mounted on/dev/mapper/data02--vg-data02--lv   50G   31G   17G  66% /aftd

adv_file device claims 100% use, 31G in use (of real 50G) and no savesets to be found.

Also daemon.log regularly shows stuff like this:

202768 02/11/25 12:35:51  nsrd NSR warning Status update: operation 'SNMD_DEVOP_CHECK_FS', instance '179', on device '/aftd' has completed abnormally with status 'DEV_OP_ERROR'.202768 02/11/25 13:20:52  nsrd NSR warning Status update: operation 'SNMD_DEVOP_CHECK_FS', instance '182', on device '/aftd' has completed abnormally with status 'DEV_OP_ERROR'.202768 02/11/25 14:05:53  nsrd NSR warning Status update: operation 'SNMD_DEVOP_CHECK_FS', instance '184', on device '/aftd' has completed abnormally with status 'DEV_OP_ERROR'.

I am asking because recently I also got mails from NW complaining about full device.

But I'm not sure what I should be seeing....

Thanks.

farnsworthy

1 Rookie

 • 

3 Posts

February 11th, 2025 16:25

No that's not normal, but it's possible it's getting hung up on the query constraint - try just a simple "mminfo -av"?

It's also possible all the savesets have expired, and if the volume backups.003 is unmounted, then the system can't purge the savesets from the filesystem.  Use the "nsrmm" command to show the status of the device and volume - looks like it may be unmounted NetWorker-wise.  If so,it can be mounted with "nsrmm -m -f /aftd".

jer0nim01

1 Rookie

 • 

15 Posts

February 11th, 2025 16:39

@farnsworthy​ 

I should maybe mention the adv_file device only contains bootstraps (because those can't go to tape directly if tapes are not locally attached)

What I also saw is the volume was mounted read-only ...

mminfo -av --> nothing

scanner gives this

# scanner /aftd
8909:scanner: using '/aftd' as the device name
8936:scanner: scanning adv_file disk backups.003 on /aftd
client name  save set             save time     level   size  files   ssid    S
nw           bootstrap            1/12/25 10:20  f 630xxxxxx   2210 yyyyyy2755 E
nw           bootstrap            1/26/25 10:21  f 645xxxxxx   2219 yyyyyy2913 E
nw           bootstrap            2/10/25 10:14  f 651xxxxxx   2248 yyyyyy695 E
nw           bootstrap            1/18/25 10:12  f 637xxxxxx   2201 yyyyyy4053 E
nw           bootstrap            1/31/25 10:13  f 649xxxxxx   2227 yyyyyy1681 E
nw           bootstrap            1/21/25 10:12  f 637xxxxxx   2204 yyyyyy0934 E
nw           bootstrap            2/02/25 10:22  f 648xxxxxx   2238 yyyyyy09 E
nw           bootstrap            2/09/25  1:47  f 650xxxxxx   2245 yyyyyy012 E
nw           bootstrap            1/05/25 10:23  f 625xxxxxx   2203 yyyyyy0989 E
nw           bootstrap            1/23/25 10:12  f 643xxxxxx   2203 yyyyyy8338 E
nw           bootstrap            1/25/25 10:12  f 644xxxxxx   2207 yyyyyy7184 E
nw           bootstrap           12/25/24 10:13  f 631xxxxxx   2192 yyyyyy581 E
nw           bootstrap            1/15/25 10:12  f 638xxxxxx   2203 yyyyyy4772 E
nw           bootstrap            2/04/25 10:13  f 646xxxxxx   2243 yyyyyy646 E
nw           bootstrap            2/01/25 10:14  f 649xxxxxx   2235 yyyyyy9245 E
nw           bootstrap            1/13/25 10:14  f 631xxxxxx   2203 yyyyyy7832 E
nw           bootstrap           12/30/24 10:17  f 625xxxxxx   2197 yyyyyy0231 E
nw           bootstrap            1/27/25 10:12  f 644xxxxxx   2210 yyyyyy2912 E
nw           bootstrap            2/07/25 10:12  f 654xxxxxx   2242 yyyyyy3079 E
nw           bootstrap            1/08/25 10:13  f 629xxxxxx   2205 yyyyyy8967 E
nw           bootstrap            1/28/25 10:13  f 645xxxxxx   2211 yyyyyy8599 E
nw           bootstrap           12/27/24 10:11  f 630xxxxxx   2196 yyyyyy4867 E
nw           bootstrap            1/16/25 10:12  f 638xxxxxx   2203 yyyyyy9040 E
nw           bootstrap            1/14/25 10:12  f 635xxxxxx   2204 yyyyyy5983 E
nw           bootstrap            1/02/25 10:12  f 627xxxxxx   2194 yyyyyy7183 E
nw           bootstrap            1/09/25 10:13  f 632xxxxxx   2205 yyyyyy3756 E
nw           bootstrap            1/19/25 10:21  f 638xxxxxx   2204 yyyyyy563 E
nw           bootstrap            1/04/25 10:17  f 626xxxxxx   2201 yyyyyy7795 E
nw           bootstrap            1/10/25 17:36  f 633xxxxxx   2207 yyyyyy75 E
nw           bootstrap            1/03/25 10:13  f 628xxxxxx   2205 yyyyyy939 E
nw           bootstrap           12/31/24 10:12  f 627xxxxxx   2193 yyyyyy0911 E
nw           bootstrap           12/24/24 10:13  f 628xxxxxx   2195 yyyyyy8602 E
nw           bootstrap            1/01/25 10:12  f 626xxxxxx   2199 yyyyyy0233 E
nw           bootstrap            1/06/25 10:16  f 624xxxxxx   2204 yyyyyy4943 E
nw           bootstrap            1/20/25 10:12  f 635xxxxxx   2207 yyyyyy4079 E
nw           bootstrap            1/22/25 10:12  f 640xxxxxx   2203 yyyyyy6160 E
nw           bootstrap            1/11/25 10:12  f 630xxxxxx   2211 yyyyyy5959 E
nw           bootstrap            1/07/25 10:13  f 627xxxxxx   2204 yyyyyy9059 E
nw           bootstrap            1/24/25 10:12  f 645xxxxxx   2204 yyyyyy8331 E
nw           bootstrap            1/10/25 10:14  f 633xxxxxx   2210 yyyyyy606 E
nw           bootstrap           12/29/24 10:21  f 625xxxxxx   2195 yyyyyy3799 E
nw           bootstrap            2/11/25 10:13  f 652xxxxxx   2240 yyyyyy645 E
nw           bootstrap           12/28/24 10:13  f 629xxxxxx   2190 yyyyyy8681 E
nw           bootstrap            1/30/25 10:13  f 647xxxxxx   2225 yyyyyy099 E
nw           bootstrap            2/06/25 10:12  f 651xxxxxx   2241 yyyyyy9215 E
nw           bootstrap            2/05/25 10:14  f 649xxxxxx   2240 yyyyyy6229 E
nw           bootstrap            2/09/25 10:20  f 650xxxxxx   2248 yyyyyy2917 E
nw           bootstrap           12/26/24 10:13  f 630xxxxxx   2198 yyyyyy2309 E
nw           bootstrap            1/17/25 10:13  f 639xxxxxx   2204 yyyyyy156 E
nw           bootstrap            2/03/25 10:14  f 643xxxxxx   2238 yyyyyy5663 E
nw           bootstrap            1/29/25 10:12  f 647xxxxxx   2225 yyyyyy8611 E
8761:scanner: done with adv_file disk backups.003

But even after setting to appendable and running "nsrim -X", the situation remains the same.

Also this results in nothing

# nsrstage -v -C -V backups.003
180169:nsrstage: Step (1 of 16): NSRCLONE_INIT_PHASE_ONE: nsrstage has been started on host 'nw', with command 'nsrstage -v -P -W backups.003 '.
180170:nsrstage: Step (2 of 16): NSRCLONE_INIT_PHASE_TWO: Obtaining nsrstage options.
180172:nsrstage: Step (3 of 16): NSRCLONE_INIT_PHASE_THREE: Performing Recover Pipe to Save disabled cloning.
180173:nsrstage: Step (4 of 16): NSRCLONE_INIT_PHASE_FOUR: Validating the command line arguments.

farnsworthy

1 Rookie

 • 

3 Posts

February 11th, 2025 22:21

@jer0nim01​ 

So this sounds bad, like the entire media db is gone, except for 1 volume?  Was scanner run before the first post?

Did nsrstage hang?  Likely can't run against a read-only volume? (but mminfo doesn't show volume as read-only, is Device RO?)

It sounds like that situation after a hard crash where a disk device is put into the state "scan needed".

But I'm going to shut up now, cuz I'm reading some stuff I've never seen before about  "a version of NetWorker server with read-only mirror".

jer0nim01

1 Rookie

 • 

15 Posts

February 12th, 2025 08:40

@farnsworthy​ 

Everything works fine except this adv_file device with the bootstraps on it.

It claims it is at 100% capacity and doesn't want to delete the expired ones.

> So this sounds bad, like the entire media db is gone, except for 1 volume?  

No

> Was scanner run before the first post?

No

> Did nsrstage hang?  

No

> Likely can't run against a read-only volume?

Probably

> (but mminfo doesn't show volume as read-only,

mminfo -m doesn't show that anyway.

Volflags showed read only (as did NMC)

> is Device RO?)

No

/dev/mapper/data02--vg-data02--lv on /aftd type ext4 (rw,relatime,data=ordered)

> It sounds like that situation after a hard crash where a disk device is put into the state "scan needed".

There was no hard crash. Butsomething on the aftd is strange.

Was this post helpful?

View All

No Events found!

Top