nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sotre out of space

sachin_sharma78

Hi all,

hope i m posting my query in rite forum. I am using only one store which is "default" right now.. today after doing some changes in my workflow when i tried to run it, i got the error that workflow cant be created as it is out of space.Even It didnt allow me to edit DCR for the same reason. I tried to run iwfsshrink command on this store without freezing it(as it is already freeezed). it showed that 6 gb space is recovered but when i saw properties of Y drive it was showing the old disk space available(i.e. 1.5 gb though it should be 7.5 gb). Again I run iwfsshrink command but before deactivating default store and activated it later. still no progress.

Can anybody help me in this matter.

Regards,
Sachin

Find more posts tagged with

Comments

Adam Stoller

Don't look at the Y: drive - look at the location where your backing store is located (run iwgetstore if you don't know) - then, in addition to that, you may need to [temporarilly] play with some of the disklow* settings in the iw.cfg file. However, ultimately if you're that close to reaching the threshhold you probably need to look into (a) getting a bigger disk and/or (b) deleting old editions.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

NathansDIS

As a matter of maintenance, how often should you delete old editions?

-nathan

Adam Stoller

It's more a matter of business requirements. How long does your business feel they need to hold on to old editions?
Some companies barely care about editions and would be happy if every edition more than a week old were deleted -- or, if they don't publish editions regularly - something like preserving only 10 editions on each branch.
Other companies have a requirement (internally or externally driven) to hold a year [or more] worth of editions.

Until you know the requirements, there isn't much point working on a solution.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

sachin_sharma78

sorry for my ignorance but my project is in initial phase and there is only one edition. Even right now i have only one branch. since i am integrating teamsite with plumtree so after approval i need to submit the file to staging area and from there deploy it to plumtree server.

My backing store is C:/iw-store and as you told me to look my backing store, it did not show any change when i ran iwsshrink. Now when I again ran the iwfsshrink command with "default"(only store in Y drive) as argument, it didn't find any duplicate file(as i had run iwfsshrink on it earlier also) and when i ran it as iw-store as argument, i got error as "Error:02005 no archive found".

my C and Y volume have 1 gb space left(though 10 days back it was 8 gb each). In last 10 days i havent made any new edition. I simply run the workflow to submit the file to staging area and from there deploy it to plumtree server. so I couldn't find any way to reduce the size of the store.

Regards,
Sachin

Adam Stoller

Again - it's not the Y drive we're interested in - that's a *virtual* file system - it's the location of the backing store - which is usally something like c:\iw-store -- the problem is that it should only be put in C: ***IFF*** there is sufficient space for between 5 and 10 times the amount of content you have to manage ***AND*** nothing else [of any note] is going to be using up disk space on that partition.

Sounds to me like what you really need to do is get another disk (with several 10s of gigs of diskspace) added to the server (let's call it F: for no very good reason, just to help differentiate it from other common drives) and then do something like this:

1. stop TeamSite processes [gracefully] so that the backing store will be in a stable state
2. perform a full copy of the entire c:/iw-store directory tree structure to f:/iw-store
(you could use OpenDeploy to do this if you enable F:/ as an allowed directory for loopback deployments)
3. Change the location where TeamSite is going to look for its backing store (I think this might be a registry setting, or perhaps a line in the iw.cfg -- it's been a while [thankfully] since I've had to work on Windows)
4. start TeamSite up again (or reboot the server and have it all come back up "normally"

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com